I think the patch below handles that fine for any mp2 builds.
I've done some more digging - this patch seems to be required.
How does it map on the thought from my previous email:
"Let's see if we can stay without making a modperl-2.0 build special. Why? Because it should use the modperl-2.0 build args for any 3rd party modules A-T runs, if it's installed and used. So it's really the same as modperl-2.0's "make test". "
Index: lib/Apache/TestRun.pm =================================================================== RCS file: /home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/TestRun.pm,v retrieving revision 1.135 diff -u -r1.135 TestRun.pm --- lib/Apache/TestRun.pm 8 Jan 2004 04:54:06 -0000 1.135 +++ lib/Apache/TestRun.pm 8 Jan 2004 21:07:01 -0000 @@ -1291,6 +1291,11 @@ sub custom_config_load { debug "trying to load custom config data";
+ if (Apache::TestConfig::IS_MOD_PERL_2_BUILD()) { + debug "modperl-2.0 build - ignore any custom config data"; + return; + } + if (my $custom_config_path = custom_config_path()) { debug "loading custom config path '$custom_config_path'";
--
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
