--recurse resolves pod links
so when you're converting one --infile into one --outfile, pod2html will use the directories from --recurse to resolve links found in --infile, otherwise it won't create html links, so if you're reading the file in a browser, there is nothing to click
since normally pod2html, if its called at all, its during make phase of module installation, to generate static html files
but if you're running a laptop and you have multiple versions of perl, this quickly eats your disk space , and scanning entire @INC every time you upgrade module starts slowing down module installs ,
so you quickly learn to disable html generation and manpage generation and switch to something like
plackup -l localhost:80 -e require(Pod::POM::Web::PSGI)
It has been years since I've relied on static pod..html files
Actually I'm mostly relying on metacpan these days for answering question around here
See also pod2html/Pod::Html/Pod::Find, podtree2html/pods2html/perl2html, pod2cpanhtml
In reply to Re: pod2html --recurse (resolves links)
by Anonymous Monk
in thread pod2html --recurse
by KeighleHawk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |