# emerge dev-perl/PodToHTML >>> cfg-update-1.8.0-r5: Building checksum index... (takes a few seconds) done! Calculating dependencies... done! >>> Emerging (1 of 1) dev-perl/PodToHTML-0.05 to / ... ... ... * checking 9 files for package collisions existing file /usr/lib/perl5/vendor_perl/5.8.8/Pod/Find.pm is not owned by this package * This package is blocked because it wants to overwrite * files belonging to other packages (see messages above). * If you have no clue what this is all about report it * as a bug for this package on http://bugs.gentoo.org package dev-perl/PodToHTML-0.05 NOT merged Searching all installed packages for file collisions... Press Ctrl-C to Stop * perl-core/PodParser-1.35: '/usr/lib/perl5/vendor_perl/5.8.8/Pod/Find.pm'
I'm looking into this - collision-protect is enabled over here and *not* complaining (but i see clearly that the files are overwriting each other, so i'm not questioning your bug report.) I plan on filing an upstream bug on this since the two modules shouldn't be overlapping, but failing that i'll remove Find.pm from PodToHTML since it is A)older and B)attempting to override a core module
fyi, this is rt #24849. I'll probably post a ticket to the podparser maintainer as well. In the meantime, I'll try and test to see if podtohtml will function without its copy of pod::find, instead relying on the podparser version.
Slight update. The only thing in portage depending on PodToHtml is VCP-autrijus. I've sent an email to Audrey to see if there is any hope of either pulling Pod::Links out (which is what she uses it for), or changing the dep. The version of Pod::Find that comes with PodToHTML bears no resemblance whatsoever to the 'real' Pod::Find distributed with perl, so I'd favor a blocker except that that doesn't resolve the issue that the version in PodToHTML is overriding the core functional one.
http://use.perl.org/~brian_d_foy/journal/32737?from=rss PodToHTML bumped in the tree, resolves the collision protect problem.
I confirm, new version emerges with no more file collision :) Thanks for your work. From article linked in comment #4 I can read: "Don't use it for anything, for though because it's dead, dead, dead." I emerged it just to try it; but if I shouldn't use it, is there an alternative package to convert POD documentation to HTML?
yes - the default pod2html that comes with perl is probably the best way. This module is in the tree because dev-perl/VCP-autrijus uses the Pod::Links module that comes with PodToHTML - not for the actual pod::html functions :)
