hi again :)
well, after giving this issue some (probably way too much) thought over the
weekend, I have decided that unless there is a -1 floating around, I'm going
to go ahead with the change as I initially suggested it.
the main reason for my going ahead is something I realized after our last
Geoffrey Young wrote:
TestRunPerl implies that mod_perl is available. If it is not,
TestRunPerl should abort *before* it creates the config file, telling
user to use a mod_perl enabled server.
I don't think it needs to be that way, and I'm not even sure it's a good
idea. here's why...
I
hi all...
I just discovered that if you use TestRunPerl to configure a third-party
module, and the installer points -apxs to an apache without mod_perl, the
test suite blows up due to mod_perl specific configuration directives in
httpd.conf.
the end result is that, within the tests,
why would you use TestRunPerl to test against not-modperl enabled
Apache? If by accident I think it is better to discover that and die
before even starting to run tests.
in a third-party (CPAN) module, you don't have much control.
say I want to test my module against mod_perl. I need to use
Geoffrey Young wrote:
why would you use TestRunPerl to test against not-modperl enabled
Apache? If by accident I think it is better to discover that and die
before even starting to run tests.
in a third-party (CPAN) module, you don't have much control.
say I want to test my module against
