On Sat, Aug 15, 2009 at 9:49 AM, Nikos Chantziaras<[email protected]> wrote: > On 08/15/2009 07:42 PM, Mark Knecht wrote: >> >> [...] >> I agree with your description, but I disagree that the upgrade >> guide is actually very clear about this. It has us upgrade the >> compiler (OK), switch to the new compiler (OK), rebuild the libtool >> stuff (OK) then then states: >> >> http://www.gentoo.org/doc/en/gcc-upgrading.xml >> >> <QUOTE> >> To be completely safe that your system is in a sane state, you must >> rebuild the toolchain and then world to make use of the new compiler. >> >> Code Listing 2.2: Rebuilding system >> >> # emerge -eav system >> # emerge -eav world >> </QUOTE> >> >> Who, reading this, wouldn't want to be safe and sane? I doesn't say >> 'might', 'could' or even 'should'. It says 'must'. > > No one knows. The devs aren't magicians :P For this specific update, there > no problems *expected*. But there's no guarantee. If you want a guarantee, > no one can give it to you other than yourself doing a rebuild of > system&world. >
Right, and hence why many people feel the need to rebuild system/world EVERY time portage maintainers release ANY version of gcc. I simply don't want to deal with the unknowns. - Mark
