On Mon, 9 Feb 2004 15:29:11 -0800 Alan <[EMAIL PROTECTED]> wrote: > I noticed that gcc 3.3 snuck into stable for x86 a few days ago with > no fanfare... > > [ebuild U ] sys-devel/gcc-3.3.2-r5 [3.2.3-r3] > > Can I assume that upgrading is painless? The move from 3.1 to 3.2 was > pretty bad IIRC due to binary incompatibility or something, but I'd > like to know if it's safe to upgrade without b0rking my server. >
My $.02. Collins' painless method is what I use: 1) emerge sync every few days 2) emerge -pUv world (I have some ~x86 packages) 3) analyze the packages offered 4) if any of the biggies are there (gcc, glibc, xfree, kde, gnome, etc.), let them age a couple of weeks and check in forums or here. 5) If you see any favorites, emerge them manually. 6) When well aged, emerge [-u | -U ] world 7) never update world withoyut checking!!! 8) if baselayout is to be updated, backup your /etc first, and do etc-update very carefully. It will offer to replace things like fstab, which is 100% fatal. <rant> I'll never understand why they do this. Lots of people have broken their systems this way. </rant> My experience has been that all too frequently something slips by the quality control process (not too surprising with all the permutations and combinations). Just check the archives for the fallout from the latest gcc, if you want a reason for going slow! I'm still sitting on a gcc and glibc update myself. Enjoy, YMMV. -- Collins - Denver Area - Gentoo stable kernel 2.6.2-rc1 -- [EMAIL PROTECTED] mailing list
