4 ms·
Nix (https://nixos.org/nix https://nixos.org/nix), probably?
by sorpaas 11y ago
Nix (https://nixos.org/nix https://nixos.org/nix), probably?
- cwp 11y agoYeah, they're getting there. The binary package cache is a start. If it cached upstream tarballs and git revs as well as builds, it would mitigate the sort of thing the OP talks about. Nix still needs some sort of distributed trust model, though. Without that, nixos.org is a single point of failure.
- manveru 11y agoYou can use your own binary caches and of course your own clone of nixpkgs repo. I think moving the binary caches to IPFS would also be a fun project.
- rdtsc 11y agoSpeaking of Nix, I just watched this video by Eric Merritt from recent Erlang Factory conf: https://www.youtube.com/watch?v=xRSFJH3Lw6I https://www.youtube.com/watch?v=xRSFJH3Lw6I He is the author of one of the popular Erlang books and here talks about using Nix in production instead of just pure langauge specific package managers (or OS package managers). Some really good insights on immutability, reproduceability, and of course real production use examples.
- wscott 11y agoYes Nix, but Nix that uses IPFS (https://ipfs.io https://ipfs.io) as a distribution medium for packages. This was a package will stay published as long as someone is using it.