On Thu, Nov 07, 2002 at 07:46:34PM -0000, Soren A wrote:
> It is conceivable (barely, at present) that I might take that one on at
> some point. I like generating HTML when building the modules but figuring
> out a general mechanism for deciding how to do so (with what options) and
> where to put the files, is a bear, isn't it.
That was the reason it was killed. No way to know the default location for
HTML docs or when its appropriate to generate and install them. The problem
is punted back to the Config folks. If they can give us a %Config value for
it then we can use it.
One simple way to avoid the problem is to only do it when explicitly given a
location.
perl Makefile.PL HTMLDIR=foo/bar
and then just provide a direct pass-through to Pod::Html. For example:
perl Makefile.PL HTMLDIR=foo/bar POD2HTMLOPT_CSS=http://localhost/foo.css
that would put HTML docs into ./foo/bar and pass
"--css" => "http://localhost/foo.css"; when invoking Pod::Html::pod2html().
While this may be cumbersome for manual usage, it at least gives automated
repackagers, like the CPAN to RPM/dpkg/ppm converters
Redhat/Debian/ActiveState use, an easy way to generate HTML docs.
The bulk of the original patch is ok, though it needs modernized to use
things like Pod::Html rather than search around for the pod2html binary.
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Playstation? Of course Perl runs on Playstation.
-- Jarkko Hietaniemi
