| 1 |
On 03/13/2015 05:08 AM, Joakim Tjernlund wrote: |
| 2 |
> On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote: |
| 3 |
>> On 03/12/2015 02:43 PM, Joakim Tjernlund wrote: |
| 4 |
>>> |
| 5 |
>>> |
| 6 |
>>> |
| 7 |
>>>> |
| 8 |
>>>>> Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing |
| 9 |
>>>>> something here, an example would be great:) |
| 10 |
>>>> |
| 11 |
>>>> It's a legacy behavior, since portage has always behaved this way, and ebuild developers have relied |
| 12 |
>>>> upon |
| 13 |
>>>> it (resulting in broken dependency calculations without it). |
| 14 |
>>> |
| 15 |
>>> Here is odd difference: |
| 16 |
>>> |
| 17 |
>>> emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources |
| 18 |
>>> ... |
| 19 |
>>> Nothing to merge |
| 20 |
>>> |
| 21 |
>> |
| 22 |
>> That's normal, because --changed-deps implies --selective (a number of options do this). If you add -- |
| 23 |
>> selective=n to the above command, you'll get the same result regardless of the --changed-deps option. |
| 24 |
> |
| 25 |
> I just did a sync and "emerge -aNDu --dynamic-deps=n --changed-deps=y --selective=n world" and |
| 26 |
> again portage wanted to rebuild > 150 pkgs. |
| 27 |
> --selective=n seems to be the culprit, should I expect this from --selective=n ? |
| 28 |
|
| 29 |
Yes --selective=n is the opposite of --noreplace, so for the above |
| 30 |
command, it will rebuild everything in /var/lib/portage/world. |
| 31 |
-- |
| 32 |
Thanks, |
| 33 |
Zac |
Archives