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

Thanks. It took me a while to understand you because of the HTML escaping in the link. I went to that URL, and yes I see a nice link to a man page. (BTW, the first link in that section, to lwp-request, is broken).

So that answers part of the question. However lwp-dump puts its POD inside the script and I'd like to have that be separate, because it may be shared/duplicated in a github wiki. So my thought was to create in the same directory the something like lwp-dump.pod.

Again I'll make a little test, and make sure to follow your guidelines and follow the format of lwp-dump.

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

Replies are listed 'Best First'.
Re^3: Getting man-page info on metacpan and search.cpan.org by Anonymous Monk on May 31, 2016 at 02:57 UTC
(BTW, the first link in that section, to lwp-request, is broken). I'm guessing, but probably because it is created at when you run Makefile.PL , so if you install LWP, the link will work, just not on CPAN update: well I checked, its a typo in the NAME section of https://metacpan.org/pod/distribution/libwww-perl/bin/lwp-request, must use dash, convention is `NAME - description` so it should be `lwp-request - GET, POST, HEAD - Simple command line user agent` [download] This is also a bug in PAUSE/CPAN indexer, most folks figure out the right formatting, but it should warn the rest when =head1 NAME doesn't match NAME - description because its used for resolving links It took me a while to understand you because of the HTML escaping in the link. Aww :) I usually double check ... metamod:// should be smarter and save me when I typo :) https://metacpan.org/pod/LWP#MORE-DOCUMENTATION	[reply] [d/l] [select]
Re^3: Getting man-page info on metacpan and search.cpan.org by rockyb (Scribe) on May 31, 2016 at 04:02 UTC
So here is the results of a test. It looks like it works, but buggy. See https://metacpan.org/source/ROCKY/Bio-BPWrapper-1.02_02/bin. Unless I've missed something, I'll report this as a bug sometime tomorrow.	[reply]
Re^4: Getting man-page info on metacpan and search.cpan.org by Anonymous Monk on May 31, 2016 at 07:25 UTC
Well, why did you do that? bioseq or https://metacpan.org/pod/bioseq leads to https://metacpan.org/pod/release/ROCKY/Bio-BPWrapper-1.02/lib/Bio/BPWrapper/bioseq.pod Delete or change the pod to `=head1 NAME Bio::BPWrapper::bioseq - desc` [download] And it "bioseq" should now lead to https://metacpan.org/pod/distribution/Bio-BPWrapper/bin/bioseq	[reply] [d/l]
Re^5: Getting man-page info on metacpan and search.cpan.org by rockyb (Scribe) on May 31, 2016 at 09:28 UTC
`bioseq` is a command-line program just like `lwp-request`. In the distribution tarball it is located in the `bin` directory. The name suggested, `Bio::BPWrapper:bioseq`, is wrong. That may be where metacpan may find it, but that is not the name. It doesn't have a package namespace of `Bio::BPwrapper`. As for why I did that, it is because I want the POD which is long to be separate from the code so that the same file can be put on a shared wiki, but combined with the distribution just before release.	[reply] [d/l] [select]
Re^6: Getting man-page info on metacpan and search.cpan.org by Anonymous Monk on May 31, 2016 at 10:27 UTC
Re^5: Getting man-page info on metacpan and search.cpan.org by rockyb (Scribe) on May 31, 2016 at 18:25 UTC
Ok. That was an inadvertent mistake on my part and explains some of the weirdness. Having gone through the possibilities listed elsehwere, I think I understand the best I can do for merging in the concerns of cpan.org and convinient wiki editing. Again this is spelled out elsewhere in this thread.	[reply]