Walt Reed wrote: > The apache part isn't the problem. I can easily run on different ports, > and whatnot. In fact, both apache's are working fine independantly, so > it's just the perl / mod_perl issue. When I do a "make install" of > mod_perl 2.x I don't want mod_perl 2 based perl modules tromping all > over the existing mod_perl 1.3 system install.
They shouldn't tromp over anything. All mod_perl2 modules are in the Apache2 namespace. Now, this doesn't guarantee that some 3rd party module won't detect that you're running under mod_perl by trying to use 'Apache2' instead of looking at $ENV, but that's a different story... -- Michael Peters Developer Plus Three, LP
