Gentoo Archives: gentoo-dev

From: Jason Stubbs <jstubbs@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Problems with emerge -g option...
Date: Mon, 29 Mar 2004 10:57:44
In Reply to: [gentoo-dev] Problems with emerge -g option... by stephen white
Hash: SHA1

On Monday 29 March 2004 19:25, stephen white wrote:
> Not sure where to report this in, so here it is... > > > sspc02 / # emerge -gupv --deep world > > [binary U ] sys-kernel/linux-headers-2.4.21-r1 [2.4.21] > > yet when I do this... > > > sspc02 / # emerge -upv --deep world > > [ebuild N ] sys-libs/db-1.85-r1 > > [ebuild N ] sys-devel/libperl-5.8.2 > > [ebuild N ] sys-apps/help2man-1.29 > > [ebuild U ] sys-kernel/linux-headers-2.4.21-r1 [2.4.21] > > [ebuild N ] dev-libs/glib-1.2.10-r5 > > [ebuild N ] app-arch/ncompress-4.2.4 > > Somehow the '-g' option is making emerge miscalculate what packages to > get.
It's actually the lack of -g option miscalculating dependencies depending on how you look at it. With the -g option, emerge ignores the USE flags that you have specified in make.conf and uses those that each binary was built with for that package. Hence, the binaries don't bring in the new packages listed above. Without the -g option, emerge will calculate the dependency tree based on your current USE flags and what is in /usr/portage regardless of the USE flags that installed packages were built with. To confirm what I'm saying, try 'USE="-*" emerge -gepv world' and you will see that any binary packages used will not have all USE flags disabled. Regards, Jason Stubbs -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iQCVAwUBQGgA0VoikN4/5jfsAQI2mgP/ZQ+nFRGWTZ1IHSzTvRPBr1T0rLbnr71o /nqDerskdOx6MHCzyznsypuP0dembPRpIw2Czn8aNU5uQb4MgFXhGHkAqALeu87K B5e+T7nrOWSrRLH3NHpyDz0NnRRU49vofA2fX+QNcPSkuq8gS4OEKjyOX+1FFX6S ejwkZxSdP/s= =4k7+ -----END PGP SIGNATURE----- -- gentoo-dev@g.o mailing list


Subject Author
Re: [gentoo-dev] Problems with emerge -g option... stephen white <steve@×××××××××××××××.au>