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(); }
?
-=Chris
smime.p7s
Description: S/MIME Cryptographic Signature