1 |
Hi, I'm gonna ask this because it's been bugging me on and off. Nothing |
2 |
too important, but i'd like to know... |
3 |
|
4 |
An example: |
5 |
|
6 |
I add ACCEPT_KEYWORDS="~x86" to my make.conf, so I can get the latest |
7 |
mozilla. |
8 |
|
9 |
Typing the command 'emerge -p mozilla' then gives me: |
10 |
|
11 |
Calculating dependencies ...done! |
12 |
[ebuild N ] x11-misc/xloadimage-4.1 |
13 |
[ebuild U ] app-crypt/gnupg-1.2.1 |
14 |
[ebuild U ] net-www/mozilla-1.2.1 |
15 |
|
16 |
Fair enough, no problem with that... but then why does issuing 'emerge |
17 |
-pu mozilla', give me: |
18 |
|
19 |
Calculating dependencies ...done! |
20 |
[ebuild U ] sys-devel/autoconf-2.54 |
21 |
[ebuild U ] sys-devel/gettext-0.11.5-r1 |
22 |
[ebuild U ] sys-apps/texinfo-4.3 |
23 |
[ebuild U ] sys-devel/gcc-3.2.1 |
24 |
[ebuild U ] sys-apps/baselayout-1.8.5.4 |
25 |
[ebuild U ] sys-devel/binutils-2.13.90.0.16 |
26 |
[ebuild U ] sys-libs/glibc-2.3.1-r2 |
27 |
[ebuild U ] sys-libs/ncurses-5.3-r1 |
28 |
[ebuild U ] sys-apps/bash-2.05b-r3 |
29 |
[ebuild U ] sys-libs/readline-4.3-r3 |
30 |
[ebuild U ] dev-libs/expat-1.95.5-r1 |
31 |
[ebuild U ] dev-lang/python-2.2.2 |
32 |
[ebuild U ] sys-apps/portage-2.0.45-r1 |
33 |
[ebuild U ] media-libs/libpng-1.2.5 |
34 |
[ebuild U ] sys-devel/flex-2.5.23 |
35 |
[ebuild U ] x11-base/xfree-4.2.1-r1 |
36 |
[ebuild N ] x11-misc/xloadimage-4.1 |
37 |
[ebuild U ] app-crypt/gnupg-1.2.1 |
38 |
[ebuild U ] media-libs/fontconfig-2.0-r4 |
39 |
[ebuild U ] dev-java/blackdown-jdk-1.4.1_beta |
40 |
[ebuild U ] net-www/mozilla-1.2.1 |
41 |
|
42 |
?! |
43 |
|
44 |
I mean, I don't need a newer X server, glibc or gcc to compile & use |
45 |
mozilla 1.2.1 ! But why the big difference between installing and updating? |
46 |
|
47 |
I would have though that -u was the correct way to update mozilla, but |
48 |
not if i've got to emerge all that lot. |
49 |
|
50 |
The only reasoning I have to go on is this from the emerge man page: |
51 |
|
52 |
(for --update) |
53 |
|
54 |
"It will not automatically update dependencies of packages in the |
55 |
world file, unless they too are in the world file." |
56 |
|
57 |
How does that explain what i'm seeing here? |
58 |
|
59 |
|
60 |
Occationally in the past, I have had the same thing happen without |
61 |
anything to do with ACCEPT_KEYWORDS="~x86", (ie just using -u on a |
62 |
normal package that there exists a newer version of). |
63 |
|
64 |
Anyone? |
65 |
|
66 |
Cheers, |
67 |
MAL |
68 |
|
69 |
|
70 |
-- |
71 |
gentoo-dev@g.o mailing list |