in reply to Re^4: Any reason to have documentation-only *.pm file instead of *.pod for CPAN distro?
in thread Any reason to have documentation-only *.pm file instead of *.pod for CPAN distro?
I'm new to POD and pod/pm interaction and precedence, please forgive my silly questions. I've just created Acme::AAA "distribution" tarball where I also included Cwd.pod to "hijack" a core module documentation. Then cpanm'd this tarball, checked with perldoc Cwd, and it printed "evil" content of my POD, not documentation extracted from Cwd.pm. Apart from, apparently, nothing prevents a "bad actor" to lure people to install something similar, but if uploaded to CPAN, what the https://metacpan.org/pod/Cwd would display then "globally"?
While we are at it, looks like perldoc link in SEE ALSO section of perlpod and elsewhere is broken in effect, it shows some obsolete Spanish translation.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^6: Any reason to have documentation-only *.pm file instead of *.pod for CPAN distro?
by soonix (Chancellor) on Jan 04, 2025 at 12:45 UTC | |
Re^6: Any reason to have documentation-only *.pm file instead of *.pod for CPAN distro?
by marto (Cardinal) on Jan 08, 2025 at 11:03 UTC |