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