On Tue, Feb 07, 2006, Larry Lansing wrote:
> [...]
> Anyway...I'm in the process of writing spec files for various
> applications I'm installing inside OpenPKG. One of the is a perl module
> with a man page, for which I would like to have the man page installed.
> I noticed that when I called Makefile.PL outside of OpenPKG, the man
> page was created and installed properly, but when I installed via the
> perl-openpkg script, the man page was not installed. After further
> investigation, I think I have identified the reason:
> [...]
> Perl-openpkg calls the 'pure_install' target instead of the 'install'
> target, in the module's generated Makefile. As far as I can tell, the
> only difference between these targets is that 'pure_install' does not
> install documentation. This seems like it was a conscious decision...if
> you don't mind, may I ask what the rationale was?
The reason simply is that with our myriad of Perl modules in the various
perl-xxx packages the <prefix>/man/ area would be totally _flooded_
with _copies_ of files (well, actually pre-rendered versions) which
already stay under <prefix>/lib/perl/ and which Perl people are used
to be read via "perldoc <module-name>" anyway. Hence we intentionally
call "pure_install" and this way avoid the redundant packaging of the
manual page information and additionally avoid the unnecessary namespace
pollution.
> Is this something that should be changed in perl-openpkg, or is it
> better for me to manually call pod2man in my spec file?
Well, I think we should keep "perl-openpkg" as is or at maximum add
an option which allows it to use "make install" instead of "make
pure_install" if wished. But unless we have more packages which need
this option I think it would be best to simply run pod2man(1) in your
*.spec file...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [email protected]
