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