Re^5: Getting man-page info on metacpan and search.cpan.org

Good suggestion. I tried that but no dice. The lib file looks nice but it is not associated with the bin.

At this point, I think the best alternative is to automate pulling in the wiki POD and stuff it into the command-line script after an __END__ just before doing a CPAN release.

Comment on Re^5: Getting man-page info on metacpan and search.cpan.org Download Code

Replies are listed 'Best First'.

Re^6: Getting man-page info on metacpan and search.cpan.org
by RonW (Parson) on Jun 03, 2016 at 21:24 UTC

The lib file looks nice but it is not associated with the bin.

What do you mean "not associated with the bin"?

I did some testing using the Perl installation on my system.

On my system, I have Perl installed in /opt - like this:

/opt/perl/bin
          lib
          site/bin
          site/lib
[download]

In site/bin there is corelist. I added a dummy corelist.pod in site/lib

Opening a xterm in my home directory, I ran perldoc corelist and got the rendering of the dummy .pod file instead of the POD in corelist

So, perldoc can find a .pod file in the library of a Perl installation.

Maybe the Makefile.PL needs to be customized to install the .pod files in lib/ instead of lib/module/path/

If CPAN and/or MetaCPAN are not displaying the .pod files in the lib/ directory of your module archive, then I think that is a bug with CPAN / MetaCPAN, since perldoc does display them as expected.</c>

[reply]
[d/l]
[select]


laziness, impatience, and hubris
	PerlMonks