On Fri, 7 Oct 2005, Andres Salomon wrote:
On Fri, 2005-10-07 at 00:16 -0500, Dave Rolsky wrote:
Package: libapache2-mod-perl2
Version: 2.0.1-4
Followup-For: Bug #329270
the standard way to provide documentation for a Perl module is to put
the POD in the module (.pm) file directly, or as a separate .pod file.
When there is a separate .pod file, it goes in the same directory as
.pm file. This allows the "perldoc" tool find it.
mp2 doesn't seem to have an install target for pod files. Thus, they
don't end up in /usr/lib/perl* next to .pm files. If you can fix this,
please provide a patch; or even better, send the patch upstream.
Aha!
Looking at the generated Makefile for mp2, I noticed a target called
"glue_pods". It looks like this goes through the API docs and
concatenates them to the end of corresponding .pm file. When I ran it
manually the .pm files under blib/lib had POD.
I don't understand the Debian build process, but I'm guessing you could
just make sure that this target gets run at some point during your build
process.
Of course, this doesn't do anything about the other (non-API) docs, but
I'm less concerned about that, since there's really no standard way to
install those anyway.
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
