that sounds like a bug. personally, I'm really irked by any 2.0 defaults in Apache::Test. I've been using it for 1.0, well, since it was made available and it's works very nicely there, but to have people always assume I'm talking about 2.0 (Apache or mod_perl) is really annoying - it should really be a generic test platform.
That's exactly why I was thinking about unimport, because Apache::Test shouldn't be able to find 2.0 stuff if Apache2 wasn't loaded (assuming that both modperls are installed), but it does find it.
yeah.
I'm going to try to rectify this problem.
I think Apache::Test should load mod_perl.pm, look at the version and act accordingly.
ok, that's reasonable. basically, look for mod_perl.pm. 2.0 modules/extensions would be required to use Apache2 themselves to account for varying installations. if that's what you mean, I agree.
Back to the issue, let's stay without unimport and announce it a bug if Apache2 was loaded when mod_perl 1.0 is used and trace who loaded it and fix the bug.
is Apache2 loaded under the hood?
<unrelated>
Unfortunately, mod_perl 1 doesn't provide any information about location of the apxs/httpd executables,
but we can fix that, no? Apache::MyConfig was recently expanded to hold lots of stuff, so I see no reason why we can't extend it to cover what we need. at least as a fallback.
so we have to rely on $ENV{APACHE} or explicit specification of httpd's location or a prompt. We no longer can do any guessing because we may pick a wrong version of httpd.
</unrelated>
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
