| 1 |
On 01/22/2018 05:14 AM, Mart Raudsepp wrote: |
| 2 |
> On Sun, 2018-01-21 at 20:24 -0800, Zac Medico wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> In sys-app/portage-2.3.20, emerge now defaults to --dynamic-deps=n. |
| 6 |
>> This |
| 7 |
>> means that unless people explicitly set |
| 8 |
>> EMERGE_DEFAULT_OPTS="--dynamic-deps=y" they're going to have to |
| 9 |
>> rebuild |
| 10 |
>> packages any time that the runtime dependencies of those packages |
| 11 |
>> need |
| 12 |
>> to be updated. It's possible to trigger these rebuilds using the |
| 13 |
>> emerge |
| 14 |
>> --changed-deps=y option. |
| 15 |
>> |
| 16 |
>> Some eclasses like autotools.eclass and vala.eclass generate |
| 17 |
>> version/slot locked dependencies that cause the dependencies of |
| 18 |
>> inheriting ebuilds to change when the versions in the eclasses are |
| 19 |
>> updated. If possible, it would be nice to avoid this version/slot |
| 20 |
>> locking. If not possible, then what should be do? |
| 21 |
> |
| 22 |
> These are mostly build time only depends, why should the user now all |
| 23 |
> of a sudden care before an unrelated rebuild or upgrade, which would |
| 24 |
> actually matter only then, not before? |
| 25 |
|
| 26 |
For various reasons, current versions of portage enable the |
| 27 |
--with-bdeps=y option by default [1]. Basically, failing to update |
| 28 |
installed packages and possibly leaving them with broken dependencies is |
| 29 |
not really a sane default behavior. |
| 30 |
|
| 31 |
[1] https://bugs.gentoo.org/598444 |
| 32 |
-- |
| 33 |
Thanks, |
| 34 |
Zac |
Archives