On 8/22/06, Adrian Frith <[EMAIL PROTECTED]> wrote:
If I am right, doesn't it mean that the whole "emerge -e system" step is pointless? Couldn't one just do "emerge -u gcc" and then "emerge -e world"? Or am I being stupid?
You are talking about when upgrading to new versions of gcc (based on your use of the -u flag), right? If so, then you are essentially correct. Indeed what I did for the last upgrade was a slightly modified version of the gcc upgrade guide [1]: emerge -u gcc gcc-config blah-blah source /etc/profile emerge --oneshot libtool revdep-rebuild --library=libstdc++.so.6 emerge --prune gcc emerge -e world The revdep-rebuild step was to rebuild all C++ applications so they link with the new C++ library. After that, I could expect my system to be sane and survive the prune of old gcc versions. The emerge -e world was to take advantage of whatever new optimizations were available. However, for someone who doesn't really know what they are doing when upgrading gcc, there is some extra safety possible with the "emerge -e system" step, since once that completes, you *know* your critical system packages have been rebuilt and still work. If you skip that and go straight to the emerge -e world, then if something fails to build, you might end up with some critical packages left behind. -Richard [1] http://www.gentoo.org/doc/en/gcc-upgrading.xml -- gentoo-user@gentoo.org mailing list
