Re: Is there a "standard" way to link to other modules in POD for a CPAN module?

Use L<Module::Name> and don't link to a specific website. The pod interpreter can then choose whichever is the best source of that module's documentation (maybe a local resource, maybe metacpan.org, whatever).

Comment on Re: Is there a "standard" way to link to other modules in POD for a CPAN module? Download Code

Replies are listed 'Best First'.
Re^2: Is there a "standard" way to link to other modules in POD for a CPAN module? by haukex (Archbishop) on May 28, 2017 at 16:58 UTC
I agree with this and just wanted to add a note: One of the POD to HTML converters (I forget which one) always turned a link like `L<File::Spec>` into something that looked like this: "the File::Spec manpage" (or something to that effect), which of course wasn't very helpful when inserted into various sentences, so I had to take to writing things like "`the L<File::Spec\|File::Spec> documentation`". A little annoying but I guess it's better to be explicit.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Is there a "standard" way to link to other modules in POD for a CPAN module?
by haukex (Archbishop) on May 28, 2017 at 16:58 UTC

I agree with this and just wanted to add a note: One of the POD to HTML converters (I forget which one) always turned a link like L<File::Spec> into something that looked like this: "the File::Spec manpage" (or something to that effect), which of course wasn't very helpful when inserted into various sentences, so I had to take to writing things like "the L<File::Spec|File::Spec> documentation". A little annoying but I guess it's better to be explicit.

[reply]
[d/l]
[select]