> Hi Shea, > > > Do you see why there are benefits [...] to having changes to stdenv > > be infrequent and more inclusive than is appropriate for a generic > > feature branch? > > of course, I totally agree with that. Stdenv should be changed only when > there is a good technical reason to do so. For example, it's one thing > to have the latest version of GNU Make available in nixpkgs, but it's > another quite thing to put it into stdenv ... or bootstrap-tools. :-) >
Ok, so when we have updated Make and gcc and glibc and all of that in nixpkgs, and we want to test it all together and give hydra something to build before we actually update stdenv to use the new tools, why not use a branch specifically made for this purpose? ~Shea > > Take care, > Peter > > _______________________________________________ > nix-dev mailing list > [email protected] > https://mail.cs.uu.nl/mailman/listinfo/nix-dev > _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
