4 ms·
https://nixos.org/guides/nix-pills/automatic-runtime-dependencies.html#idm140737320199808 https://nixos.org/guides/nix-pills/automatic-runtime-depende... Part
by kelvie 5y ago
https://nixos.org/guides/nix-pills/automatic-runtime-dependencies.html#idm140737320199808 https://nixos.org/guides/nix-pills/automatic-runtime-depende...
Part of the excellent "nix pills" guide on why things are the way they are in Nix, and why this tool was created.
The whole series is a pretty easy evening read if you have experience in functional languages (like haskell), and really helps you appreciate what nix is doing.
One of my main reservations about Nix and introducing it at work is basically requiring that other developers wrap their minds around functional concepts like partial application.
This might just be an imagined problem, but not one I want to spend cycles explaining to the higher-ups
- mikepurvis 5y agoI'm working on it now at my work, partially following some advocacy in the last Nix thread on here a month or so back. I think the biggest barrier for me is that you can't really be only partially in— like, you sort of can, but you lose a lot of the benefits if you have impure builds linking to a bunch of filesystem stuff. So yeah, you need sufficient buy-in that you can spend the effort required to basically port your entire system to a new operating system and packaging scheme. And depending how big your system is, that might be a lot of work that has to happen upfront before any real value is delivered.
- rsa25519 5y agoYou can be partially in :-) I highly recommend using the Nix package manager alongside whatever you're comfortable with. That way you can `nix shell -p foobar` when you need a package quickly or fallback to brew/apt/etc if you're not yet comfortable addressing the situation in Nix.