On Thursday 26 January 2006 08:02, Chris Gianelloni spammed: > > > > RTFM - http://www.gentoo.org/doc/en/gcc-upgrading.xml > > Except that is for an *already installed* system. > > Again, you didn't take into account the simple thing called common > sense. If you're already going to be doing an "emerge -e system" in > there, would it not make sense to: > > emerge -uav gcc > gcc-config i686-pc-linux-gnu-3.4.4 > source /etc/profile > emerge --oneshot -av libtool > emerge -eav system
You guys have made the decision to stop supporting stage1 installs. The "official" installation method is a stage3. What I documented, and tested, is what you are telling users they have to do. Download stage3, emerge --sync, update system. The only problem is that you don't actually tell the users what to do when there are major issues, such as gcc upgrades. There is no link in the handbook or the gentoo documentation page mentioning the fact that they can't just upgrade their gcc without going through the proper process you mention above. What I documented is what any user would _need_ to do to get their system installed using your recommended installation method. And those instructions have nothing whatsoever to do with common sense from a new, or even experienced users perspective. Knowing that a gcc upgrade will break libtool is not common sense, nor is it commonly known. > Remember that with a stage3 tarball, you don't *have* a world to > rebuild, so you're simply rebuilding "system" twice. Yes, but I have been called an idiot here for following the instructions given to upgrade gcc. They are not my instructions, they are not the way I would do it, they are YOUR instructions. > As I said, you're wasting your time (and ours since we're continuing to > even talk to you on this). You are certainly entitled to that opinion.
pgpSqK5gNBoX5.pgp
Description: PGP signature
