Well done, i've allready switched completely to gcc-3.4 with my main box
by reemerging about 650 packages. However, i allready started doing so a
few days ago, so I didn't read the official migration guide before
starting. Now, as everything works fine i just read this guide to
compair it with my own experiences as more or less simple user.
There are two things i have to critisize:
1.) If you remove gcc-3.3* before emerge -e system you will be left
behind with a broken python and therefore emerge. Thus i think there
should be a big red box telling users about this.
2.) emerge -e world on a system with lot of packages will most likley
fail somewhere during the process for various reasons. Fixig the problem
(for example by unmerging the package which causes it) and restarting
the process is not an option, as this may cost you lot's of time. In my
case, emerge -e world stopped 3 times. To continiue without starting it
all again, i did
# emerge --resume -p > package.list
and then edited this file with vi so that
# emerge --oneshot --nodeps `cat package.list`
continued the process, leafing out the brocken package. The be honest, i
expected to find some freaky sed command to accomplish what i did with
vi (thanks to the makro recorder) in the gcc-3.4 migration guide.
Have a nice day !
Matthias
--
gentoo-dev@gentoo.org mailing list
by reemerging about 650 packages. However, i allready started doing so a
few days ago, so I didn't read the official migration guide before
starting. Now, as everything works fine i just read this guide to
compair it with my own experiences as more or less simple user.
There are two things i have to critisize:
1.) If you remove gcc-3.3* before emerge -e system you will be left
behind with a broken python and therefore emerge. Thus i think there
should be a big red box telling users about this.
2.) emerge -e world on a system with lot of packages will most likley
fail somewhere during the process for various reasons. Fixig the problem
(for example by unmerging the package which causes it) and restarting
the process is not an option, as this may cost you lot's of time. In my
case, emerge -e world stopped 3 times. To continiue without starting it
all again, i did
# emerge --resume -p > package.list
and then edited this file with vi so that
# emerge --oneshot --nodeps `cat package.list`
continued the process, leafing out the brocken package. The be honest, i
expected to find some freaky sed command to accomplish what i did with
vi (thanks to the makro recorder) in the gcc-3.4 migration guide.
Have a nice day !
Matthias
--
gentoo-dev@gentoo.org mailing list