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