From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1Eh5v2-0006HT-UF for garchives@archives.gentoo.org; Tue, 29 Nov 2005 13:53:17 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jATDqZFJ019667; Tue, 29 Nov 2005 13:52:35 GMT Received: from smtp109.sbc.mail.re2.yahoo.com (smtp109.sbc.mail.re2.yahoo.com [68.142.229.96]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jATDom5G023428 for ; Tue, 29 Nov 2005 13:50:48 GMT Received: (qmail 67537 invoked from network); 29 Nov 2005 13:50:47 -0000 Received: from unknown (HELO ?192.168.1.5?) (curtis119@sbcglobal.net@70.226.30.153 with plain) by smtp109.sbc.mail.re2.yahoo.com with SMTP; 29 Nov 2005 13:50:46 -0000 Message-ID: <438C5CB1.5080700@gentoo.org> Date: Tue, 29 Nov 2005 08:50:41 -0500 From: Curtis Napier User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051114) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Moving GCC-3.4 to stable on x86 References: <20051128142233.GA19195@aerie.halcy0n.com> <20051129111814.GD29294@dmz.brixandersen.dk> <20051129132151.GA18947@aerie.halcy0n.com> In-Reply-To: <20051129132151.GA18947@aerie.halcy0n.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 2cf4015e-49d5-414d-bc69-53a5b1400519 X-Archives-Hash: cf64c281eea88476790d8fef01a21cce Speaking as a user who upgraded from 3.3.x to 3.4.x a loooooong loooong time ago and also as a forum mod who sees questins about this on a daily basis: Users are more or less aware that they will have to rebuild the entire world including the kernel when they upgrade gcc. If they aren't already aware of it they soon learn that it is necessary and they aren't averse to it. This is a from source distro afterall, so TELLING them in an upgrade guide that they *HAVE* to do this wouldn't be such a bad thing. It solves 99% of all the problems reported in a gcc upgrade for people who *didn't* do an "emerge -e world". Doing it from the outset will save the forums and bugs a lot of stress and heartache that could have been easily avoided. Just my 2 $DENOMINATION's -- gentoo-dev@gentoo.org mailing list