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

["Sven Köhler" <skoehler@upb.de>]

[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]

>> 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)

gcc 3.3 is only rebuild (and thereby updated) by "emerge -e system".

>> 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).
For example my stage1 inclueded gcc 3.3.5* - but 3.3.6 is already stable.

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.

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*"

The default should be the "newest" gcc.

In the above example, bootstrap.sh installs GCCV="sys-devel/gcc-3.3.6"
After that, bootstrap.sh could unmerge the gcc included in the stage1 by
	emerge -C "<$GCCV" ">$GCCV"


Greetings
  Sven


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]