Hi Lluís, >> In case there aren't, does any object to committing those two check-ins >> to trunk directly? > > Having that in trunk causes a stdenv rebuild, so a rebuild of all > stdenv.mkDerivation packages. We would have to announce such a thing.
fair enough. I guess, I'm just getting a little impatient because those changes have been hidden away in 'stdenv-updates' for quite while. > I'm working these days in the stdenv-updates branches trying to get > new platforms for NixOS. [...] I'm not sure I will have that totally > finished by next week, though. You seem to be saying that 'stdenv-updates' cannot be merged for the next two weeks, at least. Do I read that right? > What do you think, glibc 2.12 and gcc 4.5.1 for the new stdenv? If > that can be agreed, we can go on stabilizing stdenv-updates for a > later merge. To be honest, I'm not particularly interested in newer versions of glibc and gcc. I postponing those updates means that the parallel building patches can go into trunk sooner, then I'm for postponing the updates, i.e. for doing them after the merge. Alternatively, I could also commit those two patches I care about directly to trunk. Maybe that's easiest? Take care, Peter _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
