Re: 2.22 released!

On 29/05/07, Gerard Goossen <gerardtty.nl> wrote:
> Attached patch disables the install of man pages when
building by the core, by
> setting INSTALLMAN3DIR=none when calling the
Makefile.PL (maybe
> INSTALLMAN1DIR should also be set to '').
> I think this is a better, more generic way to disable
installing man
> pages when in the core.

Ooh nice idea.
However (I didn't test it) I have a remark: as I understand
it, it
prevents installation of pods, not build. So time is wasted
in
building manpages that won't be installed. Or that maybe
will be
wrongly installed (depending on what installperl does
exactly).

Is there a way to override MAN1PODS and MAN3PODS from the
Makefile.PL
command-line? and if not, shouldn't there be one, so we
could use it
there?

On Tue, May 29, 2007 at 03:58:14PM +0200, Rafael
Garcia-Suarez wrote:
> On 29/05/07, Gerard Goossen <gerardtty.nl> wrote:
> >Attached patch disables the install of man pages
when building by the 
> >core, by
> >setting INSTALLMAN3DIR=none when calling the
Makefile.PL (maybe
> >INSTALLMAN1DIR should also be set to '').
> >I think this is a better, more generic way to
disable installing man
> >pages when in the core.
> 
> Ooh nice idea.
> However (I didn't test it) I have a remark: as I
understand it, it
> prevents installation of pods, not build. So time is
wasted in
> building manpages that won't be installed. Or that
maybe will be
> wrongly installed (depending on what installperl does
exactly).
> 
> Is there a way to override MAN1PODS and MAN3PODS from
the Makefile.PL
> command-line? and if not, shouldn't there be one, so we
could use it
> there?

iirc, setting INSTALLMAN3DIR to 'none' also disables
building the pod,
at least with for normal pod files, I don't know what
happens with
custom build pod, but that probably wouldn't work with
installman,
But you find out when man files are build very quickly,
because miniperl
can't make them, so if there aren't any errors, there are no
man-pages
being build.

-- 
Gerard Goossen
TTY Internet Solutions