| 1 |
On 07/25/2013 11:29 AM, Rick "Zero_Chaos" Farina wrote: |
| 2 |
> On 07/25/2013 01:28 PM, Zac Medico wrote: |
| 3 |
>> On 07/25/2013 08:29 AM, Rick "Zero_Chaos" Farina wrote: |
| 4 |
>>>>> Shall we revisit that, and try to make portage behave more correctly, |
| 5 |
>>>>> even if it means more revbumps / rebuilding? |
| 6 |
>>> |
| 7 |
>>>> Just set EMERGE_DEFAULT_DEPS="--dynamic-deps=n" in make.conf if you'd |
| 8 |
>>>> like to test it. |
| 9 |
>>> |
| 10 |
>>> |
| 11 |
>>> What (if anything) does that break or slow down? I've had all kinds of |
| 12 |
>>> recent issues with updates breaking my autobuilds due to these issues. |
| 13 |
> |
| 14 |
>> If you use --dynamic-deps=n then you are likely to experience more |
| 15 |
>> dependency conflicts (or unsatisfied deps) triggered by installed |
| 16 |
>> packages that have since had their dependencies changed without a |
| 17 |
>> revision bump. These dependency conflicts are like the ones that you've |
| 18 |
>> experienced with binary packages [1], but they will apply to installed |
| 19 |
>> packages instead of binary packgaes. |
| 20 |
> |
| 21 |
>> [1] https://bugs.gentoo.org/show_bug.cgi?id=282927 |
| 22 |
> |
| 23 |
> |
| 24 |
> So I replace one set of dependency errors with another? This doesn't |
| 25 |
> seem all that useful... |
| 26 |
> |
| 27 |
> Perhaps we need to reevaluate how we handle these things. |
| 28 |
|
| 29 |
The advantage of using --dynamic-deps=n is that it triggers dependencies |
| 30 |
conflicts that otherwise go unnoticed, prompting you to do a revision |
| 31 |
bump in order to trigger rebuilds for people who have already |
| 32 |
build/installed the older version that now has obsolete deps. |
| 33 |
-- |
| 34 |
Thanks, |
| 35 |
Zac |
Archives