On Wed, 2006-01-25 at 22:09 +0100, Sven Köhler wrote:
> >> I'd like to see, that bootstrap.sh unmerges any old gcc
> >> (emerge -C \<${gcc package that we just compiled})
> >> so that a clean system is built with gcc 3.4 only!
> > 
> > Nope.  We don't want to remove that choice from the user.  We are
> > working now towards the 2006.0 release, which means GCC 3.3 will not be
> > present in the stage1 tarball.  Basically, wait for 2006.0, or follow
> > the standard steps to switch compilers yourself.  It's not like we're
> > forcing you to keep both compilers.  ;]
> 
> As i wrote in my other post:
> there is no choice! boostrap.sh does what it does:
> - installs gcc 3.4

Only because it is unmasked.  You could always mask 3.4 to keep it from
installing.  Yes, this is your choice.

> - leaves the gcc 3.3 from the stage1 tarball unchanged

You could also remove 3.3 after doing your bootstrap.  Remember that
part in the Handbook that says you really shouldn't be playing around
with bootstrap if you don't know what you're doing and willing to do
work on your own system?  Here's a prime example.

> So actually the first packages compiled by "emerge -e system" are
> compiled with the gcc 3.3 which came with the stage1 tarball.

Again, this is completely because of you not making any changes on your
system.

> And that "emerge -e system" updates gcc 3.3 - well, that is only a
> side-effect of other things!

Which you won't have to deal with for long, 2006.0 is being worked on as
we speak.  The basic jist of this is that what you are seeing is pretty
much expected behavior for bootstrapping using a stage with an older
GCC.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux