-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
nix-daemon: default useSandbox to true #22767
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
Conversation
@grahamc, thanks for your PR! By analyzing the history of the files in this pull request, we identified @stapelberg, @mbravenboer and @MarcWeber to be potential reviewers. |
See NixOS/nix#179. |
Is NixOS/nix#179 a blolcker on this, though? /cc @copumpkin @vcunat |
It's a policy decision, really. I think keeping sandboxes on is a better default, more in keeping with the "nix philosophy" as I interpret it, and will also get more people caring about the sandbox speed and offering to fix it 😉 |
I think it'd be a huge step forward for the 17.03 release. @edolstra are functions like |
with the approval from globin, copumpkin's enthusiasm, and vcunat's 👍 I'm taking Eelco's link as just "for reference" than an objection, and merging :) |
I'm 👎 on this. The performance problem affects everybody, while the purity issue isn't much of a big deal. |
Reverted in 7483ba0 |
I think the purity issue is a pretty big deal, but mostly outside of NixOS, so I'm not too hung up on this 😄 lack of default purity on darwin and non-NixOS linuxes can be very annoying, leading to countless hours of wasted time because some build tool "helpfully" decided to pick up something from the host's FHS filesystem. |
But Nix packages should build with and without sandboxing, since sandboxing is not compulsory. So it's not wasted time :-) |
Well, I'd like for it to become compulsory eventually (once we resolve the performance issues and the darwin sandbox problems), because those types of failures are generally quiet and very hard to diagnose, and I'd rather spend my time packaging rather than struggling with cmake's arcane rules for reaching into all sorts of places it shouldn't be looking. |
I agree it's about policy. It's machine time vs. human time. |
@edolstra i understand the efficiency argument but for those who want fast builds, they can disable sandboxing. basically a priority swap which i would like very much. |
Motivation for this change
Things done
(nix.useSandbox on NixOS,
or option
build-use-sandbox
innix.conf
on non-NixOS)
nix-shell -p nox --run "nox-review wip"
./result/bin/
)