Christopher H. Laco wrote:
Assuming it's the right thing to do, adding the mod_perl config stuff into TestSmokePerl from TestRunPerl shouldn't be too difficult.
I'm afraid of breaking anything that uses TestSmokePerl, but it doesn't appear like much, if anything does?
-=Chris
Is there any reason that TestSmokePerl can't/shouldn't use or include configure_modperl/pre_configure from TestRunPerl rather than using"
use ModPerl::Config ();
sub build_config_as_string { ModPerl::Config::as_string(); }
The two have nothing to do with each other. build_config_as_string is only used to generate reports (ala mp2bug). again, start with TestSmoke and then add overrides in TestSmokePerl if anything needs to be overriden.
-- __________________________________________________________________ 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
