[Hamish Moffatt <hamish@xxxxxxxxxxxx>]

On Thu, Jan 24, 2002 at 05:06:56PM -0500, Andrew C. Feren wrote:
> Hamish Moffatt <hamish@xxxxxxxxxxxx> writes:
> > pod2man.bat is part of the standard ActiveState Perl installation.
> > I don't understand why you wouldn't have it (and hence why we
> > can't depend on it).
> 
>         I got my perl.exe as part of a cygwin install.  I have never
>         installed perl as a separate package.  I searched my entire
>         drive for pod2man.bat and found nothing.

Oh, I wasn't aware that Cygwin included an instance of Perl. I'm
still using Cygwin B20 here (as I don't like the installation
system on newer versions), which doesn't. I wonder why they
are shipping it with some files missing.

It's a shame we can't pick up pod2man (directly) through
the path or a standard environment variable.

The same thing applies to pod2html, also. (0.9.0 doesn't use
it, but the CVS code does - more of my changes.)

>         Is there a compelling reason that relying on pod2man.bat is
>         better than calling perl with pod2man as an argument.  Perhaps
>         I am missing something.

Only that pod2man.bat will be in the path if Perl is, with ActiveState
Perl. Thus no need to change this in config.nmake if you already have 
Perl (and pod2man.bat) in your path.

>         The only advantage is you potentially only need to edit one
>         line instead of several.  Having the variable name also makes
>         it somewhat self documenting as to why that entry is in the
>         PATH.

Can you send me your suggested config.nmake again? I'll take a closer
look in light of the pod2man.bat problem.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@xxxxxxxxxx> <hamish@xxxxxxxxxxxx>