We should update stdenv-updates from trunk. Look at the logs. I may have updated it the last.
Don't hesitate updating it before or after any of your changes. We should keep the stdenv-updates to trunk merge easy. If we haven't updated it recently, it's because noone found a need for it. It is not that we want to keep it out of date from trunk. Otherwise, I also like putting temporarily the change in a different file in order not to change the current linux trunk stdenv hashes. But this may be forgotten at the time of stdenv-updates merge. Regards, Lluís. 2009/10/3 Peter Simons <[email protected]>: > Hi Ludovic, > > > The rationale is to avoid triggering full rebuilds too often, to > > save bandwidth and CPU time, and ‘stdenv-updates’ is used as a > > staging area for full-rebuild changes. > > yes, I understand the intended purpose of stdenv-updates. > Unfortunately, that branch fails to achieve its objective as a > staging area. stdenv-updates and trunk tend to diverge wildly. > Currently, both branches differ by 20,000 lines or so. What kind of > staging area is that? > > I can commit my changes to stdenv-updates, but I cannot use or test > them there. In the dubious shape that branch is in, I don't want to > use it to run any of the machines I'm responsible for. I tried that > a while ago, and felt that it was thoroughly unpleasant experience. > > 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
