[Nix-dev] hermetically sealed nixpkgs

[Roger Qiu]

Would you rather freeze the dependencies as part of whatever you're 
building, or have a persistent mirror (IPFS) of all packages that Nix 
ever makes available?

On 7/12/2015 3:44 PM, Chris Forno wrote:
> How would you go about (pre)fetching every source in the nixpkgs tree? 
> How large would you estimate the result to be (number of 
> archives/space on disk)?
>
> In the last couple days:
>
> * GNU bash silently updated patch 42 
> (https://github.com/NixOS/nixpkgs/issues/11475)
> * OpenSSL moved the 1.0.2d release to the "old" directory (breaking 
> the URL) 
> (https://github.com/NixOS/nixpkgs/commit/51a5f49d700890a93c36dd50e5eca4bf6ee6966b)
>
> These kind of breakages introduced by the external world erode the 
> promise of Nix that attracted me as a developer: reproducible builds 
> into the future. In this respect alone, Nix + a fixed nixpkgs checkout 
> provides little/no advantage over building in a VM: both work 
> indefinitely as long as you don't introduce new dependencies.
>
> I intend to build/test a sort of hermetically sealed Nix where all 
> dependencies are frozen in time (saved somewhere). I suspect I'm not 
> alone in wanting this 
> (http://permalink.gmane.org/gmane.linux.distributions.nixos/18611). 
> I'd appreciate any tips/guidance/references to related work before I 
> begin.
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev

-- 
Founder of Matrix AI
http://matrix.ai/
+61420925975

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20151215/41b78e6b/attachment.html