Skip Menu |

This queue is for tickets about the Pod-Markdown CPAN distribution.

Report information
The Basics
Id: 120452
Status: resolved
Priority: 0/
Queue: Pod-Markdown

People
Owner: RWSTAUNER [...] cpan.org
Requestors: k-rindfrey [...] gmx.de
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Links to modules for private internal or project specific need to be handeled separately
perllibmod says: "* Select a name for the module. ... If developing modules for private internal or project specific use, that will never be released to the public, then you should ensure that their names will not clash with any future public module. You can do this either by using the reserved Local::* category or by using a category name that includes an underscore like Foo_Corp::*." Actually, this is not covered by Pod::Markdown. There is no way to say 'L<This::That> links to here, L<Local:Xzy> links to there'. By default, L<This::That> are tranformed to link to metacpan, which is ok for public modules, but makes no sense for modules that are not public by definition. Thus, Pod::Markdown should have an additional attribute to specify how links like L<Local:Xzy> or L<Foo_Corp::Bar::Baz> shall be handled.
We have this same need. When generating markdown from a project’s POD: packages: L<HTTP::Tiny> ➜ $metacpanurl L<OurTool> ➜ …/docs/OurTool.md L<OurTool::Stuff> ➜ …/docs/OurTool-Stuff.md same but with links to specific part of the doc: L<HTTP::Tiny/mirror> ➜ $metacpanurl#mirror L</foo()> (in OurTool.pm) ➜ …/docs/OurTool.md#foo%28%29 L<OurTool::Stuff/bar()> ➜ …/docs/OurTool-Stuff.md#bar%28%29
3.100 has been released which accepts "local_module_url_prefix" and "local_module_re" arguments in the constructor if you want to customize perldoc urls.