Re: Bug#474529: Perl policy vs. the search order for .1{,p} manpages
On Wed, Aug 6, 2008 at 4:34 AM, Niko Tyni <ntyni@debian.org> wrote:
> while Brendan hasn't found the time to comment on this, I think moving
> .1p up on the search list would be the best thing to do for lenny at
> least. Would you still be willing to do that?
The reason that modules manual pages have distinct extensions is to
prevent filename collisions between CORE and vendo, since they share
the same manual directory. man-db fortunately has a mechanism to
select the correct page for a section: "man Foo", or "man 3 Foo" will
present the first of 3pm or 3perl which it finds.
Sadly, the shell has no such selection mechanism, so even if you do
use different extensions for section 1 pages, you will still get a
collision on the script.
http://packages.debian.org/search?suite=sid&arch=any&searchon=contents&keywords=%2Fusr%2Fbin%2Fcorelist
Is this not going to cause some large measure of grief when either of
perl or libmodule-corelist-perl upgrades?
> If a newer pod2man is going to be in a separate package (see the
> debian-perl thread), this is going to become a bit more important than
> just the libmodule-corelist-perl issue.
So this particular issue needs to be addressed.
Reply to: