| 1 |
On 05/11/2018 18:35, Rich Freeman wrote: |
| 2 |
> On Mon, Nov 5, 2018 at 11:27 AM Nikos Chantziaras <realnc@×××××.com> wrote: |
| 3 |
>> |
| 4 |
>> On 05/11/2018 17:30, Grant Edwards wrote: |
| 5 |
>>> On 2018-11-04, Nikos Chantziaras <realnc@×××××.com> wrote: |
| 6 |
>>>> On 03/11/2018 16:01, Alan Mackenzie wrote: |
| 7 |
>>>>> The developers, in this instance, failed to raise the ebuild's version |
| 8 |
>>>>> number from 1.20.3 when making this change, and also didn't notify users |
| 9 |
>>>>> by a NEWS item, that I can see. |
| 10 |
>>>> |
| 11 |
>>>> Emerge will catch this, no need for revbump. Unless you're not using -D |
| 12 |
>>>> (--deep) when updating world. Which you should. |
| 13 |
>>> |
| 14 |
>>> What do you mean "catch this"? |
| 15 |
>>> |
| 16 |
>>> I always use -D, and the change broke my system. |
| 17 |
>> |
| 18 |
>> I mean that a USE flag change will trigger a rebuild of the package |
| 19 |
> |
| 20 |
> -D will not cause USE flag changes to trigger a rebuild of a package. |
| 21 |
> |
| 22 |
> You're thinking of --newuse in this particular case. |
| 23 |
|
| 24 |
Oops, yes. I meant -N (--newuse). Not -D. Got confused. I always upgrade |
| 25 |
using: |
| 26 |
|
| 27 |
emerge -auDN --changed-deps @world |
| 28 |
|
| 29 |
The "N" was the important flag here, not the "D". |
Archives