The package dev-perl/DateManip is misnamed, and doesn't play nice with g-cpan's dependency system (it doesn't know that DateManip is "the same" as Date::Manip, which gets mapped by g-cpan to Date-Manip (with a dash between the words). This causes merge file conflicts when g-cpan tries to bring in Date-Manip to satisfy dependencies (or, if g-cpan is run first, DateManip won't merge). The only answer I see that would work for this is to rename dev-perl/DateManip to dev-perl/Date-Manip.
tove: acceptable to do: dev-perl/DateManip => dev-perl/Date-Manip?
(In reply to comment #0) > The only answer I see that would work for this is to rename dev-perl/DateManip > to dev-perl/Date-Manip. g-cpan's Portage.pm contains the distname <-> PN mapping which could be used here. In the long run, I always wanted to fix the ebuild names but was waiting for the cvs conversion. But if we want to do this now, fine for me. If we do rename the ebuilds, we should fix all of them. BTW http://cpansearch.perl.org/src/VPIT/CPANPLUS-Dist-Gentoo-0.11/lib/CPANPLUS/Dist/Gentoo/Maps.pm contains a more complete list of name mismatches.
The ebuild naming has two parts: 1. The general standard is that the gentoo name should match the distfile name. 1.1. This is very relevant where a distfile has two or more different packages. 2. Some perl modules have moved around over time, upstream distfile namechanges happening. I wasn't aware the rename list was so large :-(. With it being that large, I agree, we really want to wait for Git. So, Portage.pm usage it is :-(
Ok, I traced this down in g-cpan to the mapping data not working after the first pass. I've got a fix in the tree now, will release in 0.16.4 shortly.
0.16.4 released now.
Thanks for the fast resolution; I appreciate it.
