This is from scratch install with the new unstable thing: This is not easy, because first you have to bootstrab, and then emerge gcc and glibc, because bootstrab.sh doesn't install the newest gcc and glibc (unstable version) , this makes the bootstrab process take almost twich the amount of time. emerge binutils gettext gcc glibc && emerge binutils gettext gcc doesn't work before bootstraping, if you try to run it before bootstrab.sh it b0rks then checking for a compiler. (Not going to start over to make a report file)
If you are wanting to install these unstable packages you will _have_ to make your own profile for them as they are not included in any of our current profiles. This is why bootstrap pulled the older (stable) versions, as it looks to your profile to check which pkgs you get. The ~arch keywords do not come into play until you system is fully installed from a known profile. This may change in the future, but for now they are not in profiles.
Ok, hopefully there will be a profile in the portage tree for people running gentoo in unstable mode :)
i vaguely remember the day when we were talking about the ~arch thingy on irc and decided to go that way... somehow i got the feeling, we did that to avoid needing a new profile, but dont remember id good enough to be able to cite details. """The ~arch keywords do not come into play until you system is fully installed from a known profile. """ and why is it needed to bootstrap a normal system first? maybe because portage in stage1 is too old and does not know about ~arch? if this is the case, making a new stage1 with a current version of portage could fix it? i'm not really sure on this thingy, maybe there are other blocking reasons and i just need <no-5 mode>input, more input</no-5 mode>...
forget my guessing about old portage versions in stage1. the 1st emerge command in bootstrap.sh will update it... ;-) but if you can explain to me why ~arch only is effective after some point, please do...
Ummm Ulf: First this bug is closed and has been for a while now Secondly, LOOK at how ~arch works. now LOOK at how the profile works. bootstrap installs pkgs from your profile, and things like glibc and gcc are LOCKED DOWN in your profile. It's got nothing to do with ~arch "not working" until after you install, its got everything to do with profiles, and I for one am _not_ about to provide a profile on gcc/glibc that is untested, and I'm _not_ going to change the 1.4 profile to use them at this point. Seeeesh, of all people I thought you would be the last to ask questions like this.
My system was bootstrapped with glibc-2.3.1 and gcc-3.2-r2. You just need to edit the profile, and add "~x86" to ACCEPT_KEYWORDS.
assigned/fixed borks the database,changing to resolved:fixed. //ZhEN
