1 |
On Sat, Apr 6, 2013 at 11:09 AM, Alexis Ballier <aballier@g.o> wrote: |
2 |
> On Sat, 6 Apr 2013 11:02:14 -0400 |
3 |
> Mike Gilbert <floppym@g.o> wrote: |
4 |
> |
5 |
>> On Sat, Apr 6, 2013 at 10:33 AM, Alexis Ballier <aballier@g.o> |
6 |
>> wrote: |
7 |
>> > On Fri, 05 Apr 2013 22:18:22 -0400 |
8 |
>> > Ian Stakenvicius <axs@g.o> wrote: |
9 |
>> > |
10 |
>> >> |
11 |
>> >> Revbump -- very important in this case, as the slot-operator dep |
12 |
>> >> (iirc) does not take effect to allow sub-slot-triggered until |
13 |
>> >> after a version with the slot-operator has been emerged. |
14 |
>> >> |
15 |
>> >> So we want users to re-emerge packages either at the same time |
16 |
>> >> libpng-1.6 hits the tree, or beforehand so that they will be |
17 |
>> >> triggered for rebuild when libpng-1.6 hits. |
18 |
>> >> |
19 |
>> > |
20 |
>> > |
21 |
>> > so we force two rebuilds instead of one ? |
22 |
>> > |
23 |
>> |
24 |
>> Well, ideally you would do it in conjunction with a version bump |
25 |
>> rather than a revbump. |
26 |
>> |
27 |
>> But failing that, a revbump for an EAPI + dependency change seems like |
28 |
>> the safest option. |
29 |
>> |
30 |
> |
31 |
> or: we can do the conversion in place, tell people to |
32 |
> @preserve-rebuild / revdep-rebuild and get the benefits next time :) |
33 |
> |
34 |
|
35 |
I'm just not sure how the package managers like an in-place EAPI |
36 |
change. If it works, great. |