4 ms·
As far as I can tell Nix doesn't do dependency resolution at all [1]. Hard linking every dependency is a solution but is undecireable for most systems. I don't
by Zalastax 10y ago
As far as I can tell Nix doesn't do dependency resolution at all [1]. Hard linking every dependency is a solution but is undecireable for most systems. I don't want to specify versions for sub-dependencies so I want them to be automatic and we have the NP-problem again. It might be a smaller set of possibilities if most versions are pinned but it's still NP.
[1]: https://medium.com/@charlesstrahan/as-a-nix-nixpkgs-nixos-contributor-i-figured-id-clear-up-a-few-things-947f8583217e https://medium.com/@charlesstrahan/as-a-nix-nixpkgs-nixos-co...
- cwp 10y agoIf by "dependency resolution" you mean solving the SAT-equivalent constraint problem the article talks about, then yes, Nix does not do that. But, it does solve the simpler problem of installing a package along with the all of its transitive dependencies. Nix packages specify the exact version of each package it depends on, so you never have to recursively specify sub-dependencies. Installation is just a matter of walking an acyclic graph. It's not NP complete.