On Mon, 20 Feb 2012 20:06:12 +0100, Eelco Dolstra <[email protected]> wrote: > Hi all, > > On 20/02/12 19:52, Peter Simons wrote: > > > Modified the Python 2.7 expression so that the interpreter has unconditional > > OpenSSL support. Having OpenSSL available at the time the core interpreter > > is > > built enables all kinds of important crypto features (i.e. additional > > hashlib > > algorithms, etc.) that otherwise won't be available. > > I agree with this change, but I think we should put it in the stdenv branch > since we'll be merging that branch in a few days anyway. So I've reverted it > for now. > > P.S. with changes like this happening on a nearly daily basis now, the Nixpkgs > channel seems to be permanently lagging behind the trunk, making it rather > difficult to upgrade NixOS. And our poor buildfarm doesn't have the resources > to do full rebuilds of three Nixpkgs branches (trunk, stdenv, libpng15). It's > clearly time for a different model. For one, the Nixpkgs channel shouldn't be > auto-updated to a revision until Hydra has finished all builds for that > revision.
I have a cosmetical commit to remove the read-only empty site-packages of python. How is hydra deciding what to build? If I push it now to stdenv-updates, would it trigger another build of python or be together with the ssl commit? -- Florian Friesdorf <[email protected]> GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083 Jabber/XMPP: [email protected] IRC: chaoflow on freenode,ircnet,blafasel,OFTC
pgpYGR0XQgHdZ.pgp
Description: PGP signature
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
