1 |
On 03/14/2015 05:55 AM, Joakim Tjernlund wrote: |
2 |
> On Fri, 2015-03-13 at 10:51 -0700, Zac Medico wrote: |
3 |
>> On 03/13/2015 05:08 AM, Joakim Tjernlund wrote: |
4 |
>>> On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote: |
5 |
>>>> On 03/12/2015 02:43 PM, Joakim Tjernlund wrote: |
6 |
>>>>> |
7 |
>>>>> |
8 |
>>>>> |
9 |
>>>>>> |
10 |
>>>>>>> Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing |
11 |
>>>>>>> something here, an example would be great:) |
12 |
>>>>>> |
13 |
>>>>>> It's a legacy behavior, since portage has always behaved this way, and ebuild developers have |
14 |
>>>>>> relied |
15 |
>>>>>> upon |
16 |
>>>>>> it (resulting in broken dependency calculations without it). |
17 |
>>>>> |
18 |
>>>>> Here is odd difference: |
19 |
>>>>> |
20 |
>>>>> emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources |
21 |
>>>>> ... |
22 |
>>>>> Nothing to merge |
23 |
>>>>> |
24 |
>>>> |
25 |
>>>> That's normal, because --changed-deps implies --selective (a number of options do this). If you add -- |
26 |
>>>> selective=n to the above command, you'll get the same result regardless of the --changed-deps option. |
27 |
>>> |
28 |
>>> I just did a sync and "emerge -aNDu --dynamic-deps=n --changed-deps=y --selective=n world" and |
29 |
>>> again portage wanted to rebuild > 150 pkgs. |
30 |
>>> --selective=n seems to be the culprit, should I expect this from --selective=n ? |
31 |
>> |
32 |
>> Yes --selective=n is the opposite of --noreplace, so for the above command, it will rebuild everything in |
33 |
>> /var/lib/portage/world. |
34 |
> |
35 |
> hmm, this kind of a bummer |
36 |
|
37 |
I don't understand your motivation for using --selective=n with that |
38 |
command. Isn't the command useful without it? |
39 |
|
40 |
> --dynamic-deps=n implies --changed-deps=y which implies --selective=n |
41 |
> and this makes the whole world to rebuild. |
42 |
|
43 |
No, don't use --selective=n. I only mentioned it in order to explain the |
44 |
behavior that you observed. |
45 |
|
46 |
> Using just --dynamic-deps=n was not really safe if I understood corretly? |
47 |
|
48 |
It's safe, but you may need --changed-deps in order for your dependency |
49 |
calculations to work (depends on how the dependencies of your installed |
50 |
packages have changed). |
51 |
-- |
52 |
Thanks, |
53 |
Zac |