The solution to Bug #13083 is not mentioned in the install documentation for 1.4_rc2 (http://www.gentoo.org/doc/en/gentoo-x86-install.xml). WORKSFORME != WORKSFOREVRYONE
What exactly do you want ? Meaning, what do you want added to the install docs ? I have done 20+ bootstraps with gcc-3.2.1-r6, and they all worked flawlessly after I added the proper changes to bootstrap.sh. You are not the first to try to merge with ACCEPT_KEYWORDS="~x86" and then miss or get something wrong. Anyhow, -r6 is in stable now, so the bug or two about ~ masked packages not always getting deps properly, should no longer hold true.
How about adding "the proper changes to bootstrap.sh" to the install docs? How about adding 'USE="build bootstrap" emerge -ep gcc' (as documented in the resolution to Bug #13083) as a step in the bootstrapping process? How about adding "Do not use ACCEPT_KEYWORDS if you are bootstrapping your install?" How about adding something to /etc/make.conf that says "Do not use ACCEPT_KEYWORDS if your are bootstrapping your install?" ("IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS" doesn't count)
> How about adding "the proper changes to bootstrap.sh" to the install docs? Hello ? bootstrap.sh I fixed weeks ago on CVS (so already in rsync) to work with -r6. > How about adding 'USE="build bootstrap" emerge -ep gcc' (as documented in the > resolution to Bug #13083) as a step in the bootstrapping process? Why ? Its just to show you gcc pulls in gcc-config just fine. > How about adding "Do not use ACCEPT_KEYWORDS if you are bootstrapping your > install?" Err, usually the logic is: If you are not experienced enough to handle the consequences, stick with stable ? Just me anyhow. > How about adding something to /etc/make.conf that says "Do not use > ACCEPT_KEYWORDS if your are bootstrapping your install?" ("IF YOU ARE UNSURE > OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS" doesn't count) Once again, it is what is used to pull in unstable packages. Anybody who is totally new to something, and use the advanced stuff, and gets burned should know why ? Or at least then try stable, and see if that fixes it ? I dont see your point. You used unstable, could not handle it, and now are angry that you burnt your fingers ? Why should I add something that is totally logical all over the install docs ?
Dont know what to fix.
How about fixing the documentation to the Install Docs and the documentation to ACCEPT_KEYWORDS in /etc/make.conf? Or is that too hard? This problem didn't burn me at all. It didn't do anything more than make the install process a few minutes longer than it should have been. I'm just trying to be a good user and report bugs to the distribution devlopers in order for them to make a better more seamless distro. Obviously the Gentoo devlopers don't care about that.
Please reassign this to somebody who understand what he wants ... Im too stupid or something.
*** This bug has been marked as a duplicate of 13083 ***
Moving these so we can remove the "Install CD" component from "Gentoo Linux". I apologize to everyone for this spam, but according to the bugzilla developers, this is the only reasonable way to do this.
