nix-ld VS nix-portable

You may be interested in `nix-ld`. https://github.com/Mic92/nix-ld

As I mentioned I used nix-index to build LD_LIBRARY_PATH. I believe I picked that up from nix-ld. The README on that page shows an example and mentions some tools (nix-autobahn, nix-alien, and nix-index) to help figure it out.

Hi guys, I really like NixOS. I also do not want to miss nix-ld, because it allows me to run "normal" Linux programs on nix.

As someone who has been using NixOS for a couple of years now, I really want to say how appreciative I am of everybody for making noticeable improvements to the system on a somewhat regular basis. The nix command keeps on adding great new features like flake templates and bundling as well as just being more user friendly (error messages, actionable hints, etc.) Additionally, tools like nix-ld [1] make nix more usable than ever with software from external sources. Things just keep on getting better for NixOS users!

Despite the reputation, I feel that NixOS or some derivative of it has the power to become the best distribution for non-technical users in the long run. What NixOS has done is effectively built an interface to every component of a modern Linux system, all that needs to be built is a user application to take advantage of it. Of course, there still needs be some improvements in Nix itself for it to blossom into its final form, but I really see a path to greatness here.

I have often thought about creating a simple unified Win2K-esq or BeOS-like X11 WM/DE specifically for NixOS but unfortunately I like the time/motivation.

[1] https://github.com/Mic92/nix-ld

Regarding the ld thing, I don't know if this is relevant but probably: https://github.com/Mic92/nix-ld

Have a look at nix-ld and nix-autobahn.

There is also nix-portable (https://github.com/DavHau/nix-portable), which is basically a drop-in replacement for normal nix that does everything required for no-root operation by itself when needed. Just put the single binary in your PATH and it's ready.

level (/nix/store/)

Yes, for cache hits to happen it has to be this way as far as I remember.

There is a project called nix-portable though that I've seen some HPC users report success with:

https://github.com/DavHau/nix-portable

Great work Graham and team, I'll be switching to it on OSX.

I wonder if you took a look at some of the modifications done by portable-nix (https://github.com/DavHau/nix-portable), most important ones being:

a) Allowing user to choose the location of the nix folder (for example $HOME/.nix) by using bwrap or proot

you can install it and forget about it. yeah the major downside is that you need to disable selinux unless you use nix portable.

Yeah sadly nix-portable doesn't support macOS because of missing kernel features. They are also thinking about docker fallback though: https://github.com/DavHau/nix-portable/issues/23 🤔😋

There is this: https://github.com/DavHau/nix-portable but I agree we need an official solution

Not entirely true, there are many ways in which you can use a custom location and still take advantage of the binary cache. You can do it with chroot, file system namespaces, bind mounts and so on. There's also a nice user friendly tool that does exactly this [1].

[1]: https://github.com/DavHau/nix-portable

This is cool! In a similar vein, it's worth mentioning nix-portable is a thing. Same idea of containerization except it avoids docker. https://github.com/DavHau/nix-portable