1 |
On Sat, 26 May 2012 17:01:26 +0400 |
2 |
"Nikolaj Sjujskij" <sterkrig@×××××××.com> wrote: |
3 |
|
4 |
> > So I think the second part of this (x.y to x.y+1 transitions, in the |
5 |
> > Python world, are generally relatively smooth) invalidates your |
6 |
> > point in the first part: if the transitions are generally smooth, |
7 |
> > then yes, when Python 3.3 gets stabilized, I want all of my Python |
8 |
> > packages to be available from the 3.3 interpreter. |
9 |
> Let's take a "stable" user who updates (`emerge --update --deep |
10 |
> --newuse @world`) his/her system regularly. |
11 |
> Python 3.3 is released, added to Portage tree and eventually unmasked. |
12 |
> PYTHON_TARGETS variable is changed to include 3.3. And suddenly |
13 |
> `emerge --newuse @world` on stable system suggests rebuilding of |
14 |
> every package using new eclass, because new (though disabled) |
15 |
> USE-flags was added. And when Python 3.3 is keyworded stable, hence |
16 |
> bringing new default PYTHON_TARGETS, user should now rebuild those |
17 |
> packages once more, but now, at least, not uselessly. |
18 |
> |
19 |
> Just yesterday I had www-servers/uwsgi recompiled because of changed |
20 |
> RUBY_TARGETS. And I even have no Ruby installed. |
21 |
|
22 |
I suggest you report a bug against portage and/or PMS. |
23 |
|
24 |
-- |
25 |
Best regards, |
26 |
Michał Górny |