planning an upgrade to Perl 5.10.1 and mod_perl

Hello,

I'm planning on upgrading a large project to Perl 5.10.1 and mod_perl,
involving a dev box and 4 front-end application servers.

The 'relocation' feature of Perl 5.10 has made it clear and easy to have a 5.10
install parallel to a 5.8 install.

Now I'm planning what the mod_perl side of this might look like.

Would it mostly be as easy as re-compiling Apache with the same "configure"
arguments, but a different "--prefix" ? So, I could a parallel install
to test with, with the ability to switch between them quickly, and switch
back to the Apache/mod_perl compiled against 5.8 if I need to.

Am I missing anything major here? I realize there are some details about port
allocation that I'll need to address.

Mark

--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
mark@summersault.com Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .

Re: planning an upgrade to Perl 5.10.1 and mod_perl

Hi Mark,

> The 'relocation' feature of Perl 5.10 has made it clear and easy to have a 5.10
> install parallel to a 5.8 install.

This was always pretty easy. I've had boxes with half a dozen
different 5.8 installs on them for special purposes. You just need to
specify a path when you install perl.

> Would it mostly be as easy as re-compiling Apache with the same "configure"
> arguments, but a different "--prefix" ?

You also need to install mod_perl for each perl install. You can do
that just by running the appropriate CPAN shell or /path/to/perl
Makefile.PL for each one. You will need to give it the path to the
correct apache as well, IIRC. This stuff is baked into the Krang
installer if you want an example.

- Perrin