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