On 19-04-2008 15:31:35 +0200, Bacchella Fabrice wrote: >> So the alternative is to switch from arch to ~arch in the post-sync >> stage. Thoughts here? >> >> Questioni is now how are we going to implement this, if we all agree >> this is the way to go? Do we agree in the first place? > > I think that's a good idea. In the last 2/3 weeks, I had too many problems > with package upgrading while I was building. > > I don't know if having to upgrade all system package is a big deal. For > example, there is a lot of /usr/sfw/lib in RUNPATH left over for the > solaris build. So a re-emerge is a good thing anyway. And there a lot of > package to get after the boot strap, so it's going to be a long process > anyway.
Method A: emerge a b c emerge --sync emerge -u system emerge -e system echo 'ACCEPT_KEYWORDS="~arch"' >> make.conf emerge -e system Method B: emerge a b c emerge --sync emerge -u system echo 'ACCEPT_KEYWORDS="~arch"' >> make.conf emerge -e system Method A has the clear advantage that you'll much more likely make it to the end of the bootstrap document, however once you decide you want to do more than just system packages (quite likely), you'll basically confronted with the entire system set having newer versions (gcc, binutils, python, coreutils, to name a few larger ones). Method B is more risky, but should work if we manage not to break the life tree, which in theory shouldn't happen, but in practise not always is. Though should be easy to recover from that using emerge --sync. -- Fabian Groffen Gentoo on a different level -- [email protected] mailing list
