3 ms·
If you keep dependencies resolved at all times and operate on packages with hardcoded versions of dependencies, as Nix does, you can avoid that NP-problem. Sad
by zzzcpan 10y ago
If you keep dependencies resolved at all times and operate on packages with hardcoded versions of dependencies, as Nix does, you can avoid that NP-problem.
Sadly, I remember people involved in Go packaging discussions being dismissive of Nix's ideas.
- sagichmal 10y agoYou remember incorrectly. Nix, unfortunately, just isn't suitable for non-final dependency resolution, i.e. libraries. And that's an important part of the mandate for language packaging discussions.
- zzzcpan 10y agoNix itself isn't suitable for many things, but the ideas those guys came up with are great and work well.