-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to run system-wide Nix on systems with Nix installed #42
Comments
Sure sounds good. Feel invited to open a PR |
Never mind that, while attempting to bump the nixpkgs version I found out that static Nix binaries can now use a chroot out of the box since 2.10 I'm looking into building a Nix user experience à la |
Nixie is the result of this line of thinking, and is very close to native macOS support too! |
Interesting to see an alternative solution emerging. I'd be happy to deprecate nix-portable in favor of a better solution. Things that I like about the nixie approach which are missing from nix-portable:
Drawbacks that I currently see with nixie's approach:
What are your thoughts regarding these drawbacks? I have the following ideas how we could move the whole story forward:
Some additional ideas: |
You raise some very good points, so let me address some of the drawbacks:
As for the Docker thing, I've made sure that the script works out-of-the-box in the |
This would allow for
nix-portable
to be used in much the same way asgradlew
and be shipped with projects. On systems with Nix,nix-portable
would be able to detect and run the system-wide install of Nix instead of itself. This behaviour could be modified with a flag or environment variable.Alternatively,
nix-portable
could obtain access to the system-wide Nix store or talk to the system-wide Nix daemon if it detects it, so that the sandbox is retained, but the risk of data duplication is reducedThe text was updated successfully, but these errors were encountered: