Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable

[Mike Frysinger]

On Wednesday 25 January 2006 15:44, Sven Köhler wrote:
> >> I'd like to see, that bootstrap.sh unmerges any old gcc
> >> (emerge -C \<${gcc package that we just compiled})
> >
> > that's a bad idea imo
> > let the user decide which gcc they wish to have
>
> So i understand what you're trying to tell me, but bootstrap.sh makes
> the choice already:
> bootstrap.sh only rebuilds gcc 3.4
> (i looked that up in my emerge.log)

you're looking at bootstrap wrong ... it forces a few native packages to the 
newest version available

in this case, bootstrap emerges gcc and portage picks the best one ... 
gcc-3.4.4

> >> so that a clean system is built with gcc 3.4 only!
> >
> > it wouldnt anyways as the version of gcc isnt changed unless the user
> > does so
> >
> > so unless you ran `gcc-config 3.4.4`, your gcc version would still be
> > 3.3.x
>
> Right, and it will be the gcc 3.3 included in the stage1 tarball - even
> if a new gcc 3.3 version is available. So if the user wants to use gcc
> 3.3, he has to manually update gcc (for example to have features not
> included in the gcc from the stage1 tarball).

if a user wants gcc-3.3 but not gcc-3.4, then it's their responsibility to 
mask it accordingly via /etc/portage

> So no matter if the user wants gcc 3.3 or gcc 3.4, the user has to do
> something manually to get a "proper" gentoo.

i dont know what you mean by "proper"

at any rate, this will all "fix" itself when 2006.0 is released

> If i may suggest something, then i would recomm that the user is abled
> to specify the gcc installed by bootstrap.sh like this:
> 	bootstrap.sh --gccspec "=sys-devel/gcc-3.3*"

no, use /etc/portage
-mike

-- 
gentoo-dev@g.o mailing list