On Saturday 03 December 2005 21:47, Duncan wrote: > 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!
This is incorrect. Portage should only restart if the version that was merged does not match the internally recorded version. There was one or two releases that had an incorrect internal version but not for at least a year. However, if the version has changed and portage does restart itself then any packages listed before portage will be merged again. > 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.) Perhaps you were using one of the broken versions? -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list
