Hi Michael, >> Eventually, you decide that the new glibc is stable, and then you >> run "git merge stdenv/glibc" on whatever happens to be your >> equivalent of the official master branch, and then you push the >> changeset upstream, which effectively makes them "stable" for >> everyone. > > Right, and the "make" change keeps hanging. So we are worse off than > now, because we get two stdenv rebuilds.
actually, it's exactly the opposite. We are better off because we have significantly reduced the amount of inference between changes to GNU Make and changes to GNU libc. When the glibc update has been pushed, those changes become "stable" or "official" or however you want to call it, meaning that those changes are going to be propagated into all active stdenv/* topic branches, where the people working on those branches can address problems the glibc update might cause locally. If all these changes were to occur in a single branch, then those changes would constantly interfere with each other, causing lots and lots of unnecessary re-builds and making everyone's live much harder. Take care, Peter _______________________________________________ nix-dev mailing list nix-dev@cs.uu.nl https://mail.cs.uu.nl/mailman/listinfo/nix-dev