Hi Lluís, > If you want to build a derivation with the derivation of an older > boost, you should write an expression for that, maybe in ~/.nixpkgs.
that approach is not particularly satisfying. Free software ought to be shared. When you write a Nix expression that's useful to you, chances are that it will be useful to others, too. Keeping that expression to yourself means that others will have to re-invent the wheel. That's not a good idea. Also, other people sometimes contribute fixes, patches, use-cases, and ideas, and by doing so help improve the expression. That wouldn't be possible if the code wouldn't be shared. The primary platform for sharing Nix expressions is the nix-pkgs repository. So, when I write an expression, I'd like that expression to be distributed in nix-pkgs. If that turns out to be impossible, then I see very little point in writing a Nix expressions to begin with; then I'd rather choose a package description format that allows me to collaborate with others (i.e. PKGBUILD). > People not updating often, may end up with more than one version of boost > installed, so the use of disk space can be beyond the 258 MB. You are right. People, who do not run nix-collect-garbage(1) regularly may need more disk space than people who do. Take care, Peter _______________________________________________ nix-dev mailing list nix-dev@cs.uu.nl https://mail.cs.uu.nl/mailman/listinfo/nix-dev
