On 01/22/2018 12:24 AM, Alexis Ballier wrote: > On Sun, 21 Jan 2018 23:01:08 -0800 > Zac Medico <[email protected]> wrote: > >> Please review. >> >> Title: Portage Dynamic Deps >> Author: Zac Medico <[email protected]> >> Posted: 2018-01-28 >> Revision: 1 >> News-Item-Format: 2.0 >> Display-If-Installed: <sys-apps/portage-2.3.20 >> >> Beginning with Portage 2.3.20, the previous default --dynamic-deps=y >> setting has changed to --dynamic-deps=n. Due to this change, some >> users may experience emerge dependency calculation failures triggered >> by installed packages that have outdated dependencies. In order to >> avoid problems of this nature, use the emerge --changed-deps=y option >> with your next deep @world update. > > What's the rationale behind this ? > > What I mean is: while '--dynamic-deps=n --changed-deps=n' is the > technically correct behavior, this just seems like throwing unbearable > dep calculation failure messages at users' faces while we could default > to '--dynamic-deps=n --changed-deps=y' and get the already > policy-mandated behavior of 'force a rebuild when you change deps'.
It depends on how difficult it is to enforce the revision bumps. If it's really difficult, then it does make sense to enable --changed-deps=y by default. -- Thanks, Zac
signature.asc
Description: OpenPGP digital signature
