> "ml" == martin langhoff <[EMAIL PROTECTED]> writes:
ml> this helps me reduuce the time it takes to up/down-grade perl, for
ml> instance. or mod_perl, maybe. I guess we all should have a list like
ml> that, and it'd be useful to share it and cross-pollinate ideas/modules.
These are know
I guess I will chime in on this since we have dealt with this very same issue.
The problem that we have is that there are a handful of production boxes, a
handful of staging boxes (testing release candidates etc), and a handful of
developer boxes.
Our goal was to make it as easy as possible to g
martin langhoff wrote:
>
> hi,
>
> i guess once you've been playing with mod_perl for a while, you
> certainly installed perl, many modules, plus mod_perl, plus apache, plus
> many more things ...
>
> I keep a personal list of all the modules I must d/l and install on a
> virgin
I guess that's good and true for those with low-cost + hi-speed +
reliable connections. I have a few servers in here, and a dial-up
connection i'd rather be careful about ;)
anyway, I find it's very important to know all the modules I'm
needing/using. Is it me?
on the oth
I always thought that if you did a CPAN installation of mod_perl, it
automatically downloaded the modules that it needed. Am I wrong ?
martin langhoff <[EMAIL PROTECTED]> writes:
> what do you think? is it already done? maybe all of a sudden I've got
> this oh so great idea just because I have not read the instructions to
> download the latest bundle from CPAN.
An expansion on Stas' "10 lines to installing mod_perl" in
