| 1 |
On 01/22/2018 12:24 AM, Alexis Ballier wrote: |
| 2 |
> On Sun, 21 Jan 2018 23:01:08 -0800 |
| 3 |
> Zac Medico <zmedico@g.o> wrote: |
| 4 |
> |
| 5 |
>> Please review. |
| 6 |
>> |
| 7 |
>> Title: Portage Dynamic Deps |
| 8 |
>> Author: Zac Medico <zmedico@g.o> |
| 9 |
>> Posted: 2018-01-28 |
| 10 |
>> Revision: 1 |
| 11 |
>> News-Item-Format: 2.0 |
| 12 |
>> Display-If-Installed: <sys-apps/portage-2.3.20 |
| 13 |
>> |
| 14 |
>> Beginning with Portage 2.3.20, the previous default --dynamic-deps=y |
| 15 |
>> setting has changed to --dynamic-deps=n. Due to this change, some |
| 16 |
>> users may experience emerge dependency calculation failures triggered |
| 17 |
>> by installed packages that have outdated dependencies. In order to |
| 18 |
>> avoid problems of this nature, use the emerge --changed-deps=y option |
| 19 |
>> with your next deep @world update. |
| 20 |
> |
| 21 |
> What's the rationale behind this ? |
| 22 |
> |
| 23 |
> What I mean is: while '--dynamic-deps=n --changed-deps=n' is the |
| 24 |
> technically correct behavior, this just seems like throwing unbearable |
| 25 |
> dep calculation failure messages at users' faces while we could default |
| 26 |
> to '--dynamic-deps=n --changed-deps=y' and get the already |
| 27 |
> policy-mandated behavior of 'force a rebuild when you change deps'. |
| 28 |
|
| 29 |
It depends on how difficult it is to enforce the revision bumps. If it's |
| 30 |
really difficult, then it does make sense to enable --changed-deps=y by |
| 31 |
default. |
| 32 |
-- |
| 33 |
Thanks, |
| 34 |
Zac |
Archives