Starting with 2.4, Apache needs to read its configuration file even to
report its version and build parameters with the "-V" option, probably
because the MPM module can be chosen at run time.
However, the system Apache configuration may not be available to the user
building mod_perl, or it may depend on special environment variables or
the like. The attached proposed patch makes Apache-Test use the test
configuration file and server root instead for the "-V" invocations,
if those are available.
I don't see any reason why this shouldn't be safe to use with earlier
versions of Apache too. Everything works for me with Apache 2.2 too FWIW.
We're currently using this for the Debian package, to run the test suite
in package builds with a controlled httpd config instead of relying on the
system one.
--
Niko Tyni ntyni@debian.org
report its version and build parameters with the "-V" option, probably
because the MPM module can be chosen at run time.
However, the system Apache configuration may not be available to the user
building mod_perl, or it may depend on special environment variables or
the like. The attached proposed patch makes Apache-Test use the test
configuration file and server root instead for the "-V" invocations,
if those are available.
I don't see any reason why this shouldn't be safe to use with earlier
versions of Apache too. Everything works for me with Apache 2.2 too FWIW.
We're currently using this for the Debian package, to run the test suite
in package builds with a controlled httpd config instead of relying on the
system one.
--
Niko Tyni ntyni@debian.org
