1 |
On Friday 02 June 2006 18:33, Allan Gottlieb wrote: |
2 |
> At Fri, 02 Jun 2006 00:29:10 +0100 Neil Bothwick <neil@××××××××××.uk> wrote: |
3 |
> > On Fri, 2 Jun 2006 00:48:21 +0200, Hemmann, Volker Armin wrote: |
4 |
> >> > You'll need to add --update --deep to catch packages affected by the |
5 |
> >> > changed USE flags. |
6 |
> >> |
7 |
> >> no you have not: |
8 |
> >> |
9 |
> >> emerge -a --newuse world |
10 |
> >> |
11 |
> >> >>> --newuse implies --update... adding --update to options. |
12 |
> >> |
13 |
> >> and I can't remember that this was different in the past. |
14 |
> > |
15 |
> > Yes it was. Adding --update pulled in extra packages, even though they |
16 |
> > were the same version as installed. This was somewhat counter-intuitive, |
17 |
> > so the new behaviour makes more sense. You should still need --deep |
18 |
> > though. |
19 |
> |
20 |
> Which version of emerge/portage is being discussed? I am running |
21 |
> portage-2.0.54-r2. The man page for emerge suggests (but does not |
22 |
> state) that --update is still needed. |
23 |
> |
24 |
> --update (-u) |
25 |
> |
26 |
> Updates packages to the best version available, which may not |
27 |
> always be the highest version number due to masking for |
28 |
> testing and development. This will also update direct |
29 |
> dependencies which may not be what you want. In general, use |
30 |
> this option only in combination with the world or system |
31 |
> target. |
32 |
> |
33 |
> I also don't see an explicit mention that --newuse implies --update |
34 |
|
35 |
it is not in the manpage, but emerge tells it: |
36 |
emerge -pN world |
37 |
>>> --newuse implies --update... adding --update to options. |
38 |
|
39 |
These are the packages that would be merged, in order: |
40 |
|
41 |
Calculating world dependencies |
42 |
. |
43 |
. |
44 |
. |
45 |
|
46 |
-- |
47 |
gentoo-user@g.o mailing list |