On Tue, Feb 12, 2002 at 10:34:09AM -0500, Andy Dougherty wrote:
> On Tue, 12 Feb 2002, Michael G Schwern wrote:
>
> > I'm working on the htmlifypods target in MakeMaker and I came upon a
> > little problem. Where should HTMLified docs be installed to by
> > default? That is, what should the INSTALLHTML*DIR macros be set to?
>
> The intent was that there would be 3 hierarchies of directories:
>
> =item Directories for the perl distribution
> =item Directories for site-specific add-on files
> =item Directories for vendor-supplied add-on files
<snip>
Ok, that clears things up, thanks. I'm still curious where
ActiveState is using $Config{installhtmldir}.
> For MakeMaker, I would think it ought to check for (and honor) the
> install*html*dir variables if they exist, but if they don't exist, it
> has to fall back on inspired guessing. I couldn't say offhand whether
> the current inspired guessing is good, bad, or indifferent as I have
> never looked at it.
The current behavior is if the variables aren't there, it goes and has
lunch. htmlifypods is left a no-op. This is Bad because even if you
later try something like:
INSTALLHTMLSITELIBDIR=/foo make htmlifypods
its still a no-op.
Here's my plan. I'm going to chop out htmlifypods, INST_HTML* and
INSTALLHTML* completely. Since its been two and a half years and this
feature still isn't completed, I'll chalk it up to Murder By Apathy.
If later on someone wants to try and have MakeMaker install HTML docs,
they can at least have the benefits of a clean slate.
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
There is nothing wrong. We have taken control of this sig file. We will
return it to you as soon as you are groovy.
