Mark Loeser posted <[EMAIL PROTECTED]>, excerpted below, on Fri, 02 Dec 2005 16:55:23 -0500:
> [1] http://www.gentoo.org/proj/en/base/x86/gcc-upgrading-guide.xml Reading this reminds me of a question I've had since I tried emerge -eav world last time: When portage merges, it stops the emerge process, updates its metadata or whatever, then restarts the process. With the -e in there, at least here, it reissued the same command over again, thereby restarting the process from the beginning and of course, upon getting to portage, looping yet again! I don't know how many times it looped before I decided to check on things and figured out what was happening, at which point I was able to do an emerge -pe and get a listing, then delete <=portage from the list and just remerge what came after. I've yet to see anyone else mention this, and certainly the document above doesn't mention it as an issue when invoking emerge -e world, so that reasonably means I experienced the loop when others don't. Why might this be (I know the reason for portage stopping and recalculating, but why is it apparently not hitting others), and what can I do to prevent it the next time I do an emerge -e world? Maybe it was because I was using -KuD also, to remerge/upgrade from binary packages? (Hard disk trouble, I was remerging the binary packages to bring up2date an old installation snapshot.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
