1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Monday 29 March 2004 19:25, stephen white wrote: |
5 |
> Not sure where to report this in bugs.gentoo.org, so here it is... |
6 |
> |
7 |
> > sspc02 / # emerge -gupv --deep world |
8 |
> > [binary U ] sys-kernel/linux-headers-2.4.21-r1 [2.4.21] |
9 |
> |
10 |
> yet when I do this... |
11 |
> |
12 |
> > sspc02 / # emerge -upv --deep world |
13 |
> > [ebuild N ] sys-libs/db-1.85-r1 |
14 |
> > [ebuild N ] sys-devel/libperl-5.8.2 |
15 |
> > [ebuild N ] sys-apps/help2man-1.29 |
16 |
> > [ebuild U ] sys-kernel/linux-headers-2.4.21-r1 [2.4.21] |
17 |
> > [ebuild N ] dev-libs/glib-1.2.10-r5 |
18 |
> > [ebuild N ] app-arch/ncompress-4.2.4 |
19 |
> |
20 |
> Somehow the '-g' option is making emerge miscalculate what packages to |
21 |
> get. |
22 |
|
23 |
It's actually the lack of -g option miscalculating dependencies depending on |
24 |
how you look at it. |
25 |
|
26 |
With the -g option, emerge ignores the USE flags that you have specified in |
27 |
make.conf and uses those that each binary was built with for that package. |
28 |
Hence, the binaries don't bring in the new packages listed above. |
29 |
|
30 |
Without the -g option, emerge will calculate the dependency tree based on your |
31 |
current USE flags and what is in /usr/portage regardless of the USE flags |
32 |
that installed packages were built with. |
33 |
|
34 |
To confirm what I'm saying, try 'USE="-*" emerge -gepv world' and you will see |
35 |
that any binary packages used will not have all USE flags disabled. |
36 |
|
37 |
Regards, |
38 |
Jason Stubbs |
39 |
-----BEGIN PGP SIGNATURE----- |
40 |
Version: GnuPG v1.2.4 (GNU/Linux) |
41 |
|
42 |
iQCVAwUBQGgA0VoikN4/5jfsAQI2mgP/ZQ+nFRGWTZ1IHSzTvRPBr1T0rLbnr71o |
43 |
/nqDerskdOx6MHCzyznsypuP0dembPRpIw2Czn8aNU5uQb4MgFXhGHkAqALeu87K |
44 |
B5e+T7nrOWSrRLH3NHpyDz0NnRRU49vofA2fX+QNcPSkuq8gS4OEKjyOX+1FFX6S |
45 |
ejwkZxSdP/s= |
46 |
=4k7+ |
47 |
-----END PGP SIGNATURE----- |
48 |
|
49 |
-- |
50 |
gentoo-dev@g.o mailing list |