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. Unfortunately, the way the documentation is packaged in libapache2-mod-perl2-doc doesn't really resolve this bug, because it sticks gzipped pod in the /usr/share/doc/libapache2-mod-perl2-doc tree, where perldoc will never see it. To really resolve this bug, I think the .pod files need to go in appropriate directory next to the .pm files they document. Finally, I think the API docs need to go in the libapache2-mod-perl2 package along with the modules they document. Putting the "extra" docs in the -doc package seems fine though. Sorry to nag about this, but the package really is really incomplete without perldoc-accessible documentation. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf-8) Versions of packages libapache2-mod-perl2 depends on: ii apache2-common 2.0.54-5 next generation, scalable, extenda ii libapr0 2.0.54-5 the Apache Portable Runtime ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii libdb4.2 4.2.52-20 Berkeley v4.2 Database Libraries [ ii libdevel-symdump-perl 2.03-3 Perl module for inspecting perl's ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libldap2 2.1.30-12 OpenLDAP libraries ii libperl5.8 5.8.7-5 Shared Perl library ii liburi-perl 1.35-1 Manipulates and accesses URI strin ii libwww-perl 5.803-4 WWW client/server library for Perl ii perl [libmime-base64-perl] 5.8.7-5 Larry Wall's Practical Extraction ii perl-base [perlapi-5.8.7] 5.8.7-5 The Pathologically Eclectic Rubbis libapache2-mod-perl2 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
