Since we don't install manpages perl ebuilds anymore we should inform users about this.
Created attachment 83604 [details, diff] perl-module.eclass.patch --- /usr/portage/eclass/perl-module.eclass 2006-04-01 13:34:35.234285750 +0200 +++ /usr/portage/eclass/perl-module.eclass_patched 2006-04-01 13:34:29.897952250 +0200 @@ -178,6 +178,7 @@ } perl-module_pkg_postinst() { + einfo "We don't install man pages w/ perl ebuilds at all, was causing nasty collisions. Use perldoc instead." updatepod }
I'll admit to being torn on this, namely becaue if you know you want to look at documentation for a specific perl module, then you know what perldoc is. We didn't disable the generation of man pages, we disabled the forced conversion of pods to man (not quite the same thing). For instance, spamassassin still generates man pages for everything, its only the pod->man process that's been disabled. I've yet to see one bug - or anyone really notice - that there aren't a zillion man pages duplicating the inline pods yet. Don't misunderstand me, if the concesus is to add this note I will do it, but I think its misleading.
...and then bug 128363 comes along. I'm still opposed (it's been like 10 seconds since my last post on this bug). i'll add the note. still grumbling. perldoc is more reliable.
done
