Nix Derivation Madness

Re:Nix Derivation Madness by gf000 on Saturday November 01, 2025 @04:59AM (#45780230)

I'm afraid this doesn't work in a generic Unix world -- what stops an application from saving some env variable it was first initialized with into its local config and later accessing them (and potentially failing if they were GCd in the meanwhile)? E.g. many developer tools store references to compilers and the like.

[ Parent | on HN ]

Re:Nix Derivation Madness by Ericson2314 on Saturday November 01, 2025 @11:33PM (#45787673)

Nix is over 20 years old. We've fought all those tools and won by now. (I.e. we've figured out how to configure them to not do that when we don't want them too.)

[ Parent | on HN ]

Re:Nix Derivation Madness by gf000 on Sunday November 02, 2025 @02:16AM (#45788439)

I am using Nix everywhere and have some packages contributed, so I do know how it goes - and there absolutely are cases like I have mentioned. Sure, apps can be patched, problems can be circumvented, but a fundamentally malicious/ignorant program can end up a pain in the ass for nix to manage (without bringing out the big guns like build FHS env)

[ Parent | on HN ]