Using the --deep option for emerge -u --deep world, I seem to be jumping back and forth between ExtUtils-MakeMaker version 6.03-r1 and 6.05. Let me explain. I am assuming that I started with 6.03-r1 (fair assumption) since I have done this so many times now that I don't know which version I started with. If I do, emerge -up --deep world, (which incidentally is the same output as emerge -up world), I get: These are the packages that I would merge, in order. Calculating world dependencies ...done! [ebuild U ] dev-perl/ExtUtils-MakeMaker-6.05 So, I go ahead and do an emerge -u --deep world and it builds 6.05 but never adds it into the world file. Now, if I want to clean out stale packages, I do an "emerge -cp" and get the otuput: >>> These are the packages that I would unmerge: dev-perl/ExtUtils-MakeMaker selected: 6.03-r1 protected: 6.05 omitted: none I go ahead and issue an "emerge -c". Note that ExtUtils-MakeMaker is still not in the world file. Now, issuing a "emerge -up --deep world", again points me back to 6.03-r1, as follows: These are the packages that I would merge, in order. Calculating world dependencies ...done! [ebuild U ] dev-perl/ExtUtils-MakeMaker-6.03-r1 and then the cycle continues. emerge -up --deep world points me to an update for 6.05. After updating I issue an emerge -c and it cleans out 6.03-r1 and we're back to where we started. I am on gcc3.2 on a pentium4 which was converted from a gentoo 1.2 to gentoo 1.4 using the update scripts.
I just did a grep for dev-perl in /var/cache/edb/world and found the following packages: dev-perl/gtk-perl dev-perl/SGMLSpm dev-perl/XML-RegExp Furthermore, the directory /usr/portage/metadata/cache/dev-perl has the following files which have the string =dev-perl/ExtUtils-MakeMaker-6.03-r1 and which are also available in my "world" file: gtk-perl-0.7008-r4 XML-RegExp-0.03 Does this help explain, the whole issue?
Unfortunately, no. I grepp'd the entire portage tree and could only find one direct dependancy on ExtUtils-MakeMaker, and that one wasn't version specific.
I wouldn't worry about it any more since it hasn't happened lately. So we can close this bug.