Gentoo Archives: gentoo-python

From: "Michał Górny" <mgorny@g.o>
To: Nikolaj Sjujskij <sterkrig@×××××××.com>
Cc: gentoo-python <gentoo-python@l.g.o>, Dirkjan Ochtman <djc@g.o>
Subject: Re: [gentoo-python] python-distutils.eclass vs. python.eclass + distutils.eclass
Date: Sat, 26 May 2012 13:07:41
Message-Id: 20120526150729.033dcd82@pomiocik.lan
In Reply to: Re: [gentoo-python] python-distutils.eclass vs. python.eclass + distutils.eclass by Nikolaj Sjujskij
On Sat, 26 May 2012 17:01:26 +0400
"Nikolaj Sjujskij" <sterkrig@×××××××.com> wrote:

> > So I think the second part of this (x.y to x.y+1 transitions, in the > > Python world, are generally relatively smooth) invalidates your > > point in the first part: if the transitions are generally smooth, > > then yes, when Python 3.3 gets stabilized, I want all of my Python > > packages to be available from the 3.3 interpreter. > Let's take a "stable" user who updates (`emerge --update --deep > --newuse @world`) his/her system regularly. > Python 3.3 is released, added to Portage tree and eventually unmasked. > PYTHON_TARGETS variable is changed to include 3.3. And suddenly > `emerge --newuse @world` on stable system suggests rebuilding of > every package using new eclass, because new (though disabled) > USE-flags was added. And when Python 3.3 is keyworded stable, hence > bringing new default PYTHON_TARGETS, user should now rebuild those > packages once more, but now, at least, not uselessly. > > Just yesterday I had www-servers/uwsgi recompiled because of changed > RUBY_TARGETS. And I even have no Ruby installed.
I suggest you report a bug against portage and/or PMS. -- Best regards, Michał Górny


File name MIME type
signature.asc application/pgp-signature


Subject Author
Re: [gentoo-python] python-distutils.eclass vs. python.eclass + distutils.eclass Nikolaj Sjujskij <sterkrig@×××××××.com>