Sreeji K Das wrote:
[...]
Hm... Actually I manage the techstack for our
development and production servers. The idea was we'll
have a document & blindly following the document,
anyone can manage the techstack (even those who don't
have much idea about mod_perl/apache & other
components). So we plan
--- Stas Bekman <[EMAIL PROTECTED]> wrote: > Sreeji K >
>>Why not do the simple:
> >>
> >>perl Makefile.PL `cat
> >>/whereever/your/file/is/makepl_args.mod_perl`
> >
> Then I lose the flexibility of having comments &
neat
> formatting in the config. file. I'll have to escape
> all the newlines.
Sreeji K Das wrote:
--- Stas Bekman <[EMAIL PROTECTED]> wrote: > Sreeji K
Das wrote:
mod_perl build currently requires that
makepl_args.mod_perl is present in one of
current, '..' or $ENV{HOME}.
...
Why not do the simple:
perl Makefile.PL `cat
/whereever/your/file/is/makepl_args.mod_perl`
--- Stas Bekman <[EMAIL PROTECTED]> wrote: > Sreeji K
Das wrote:
> mod_perl build currently requires that
> makepl_args.mod_perl is present in one of
> > current, '..' or $ENV{HOME}.
> ...
> Why not do the simple:
>
> perl Makefile.PL `cat
> /whereever/your/file/is/makepl_args.mod_perl`
Then
Sreeji K Das wrote:
Hi Guys
How many of you use makepl_args.mod_perl ? I have a
file handy with all the required options & I build a
static httpd with a single 'perl Makefile.PL'. I have
found this method very convenient. However, mod_perl
build currently requires that makepl_args.mod_perl is
pres
Sreeji K Das wrote:
Hi Guys
How many of you use makepl_args.mod_perl ?
I do.
I have a
file handy with all the required options & I build a
static httpd with a single 'perl Makefile.PL'. I have
found this method very convenient. However, mod_perl
build currently requires that makepl_args.mod_pe
