>> 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 - leaves the gcc 3.3 from the stage1 tarball unchanged So actually the first packages compiled by "emerge -e system" are compiled with the gcc 3.3 which came with the stage1 tarball. And that "emerge -e system" updates gcc 3.3 - well, that is only a side-effect of other things!
signature.asc
Description: OpenPGP digital signature
