> so you are looking at encountering other > problems, as you try to run modperl tests without using a correct > environment.
yeah, you're right. >>> or something else needs to be done with t/more. yes. well, with Apache/Test.pm actually. this should be more helpful: Index: lib/Apache/Test.pm =================================================================== --- lib/Apache/Test.pm (revision 122981) +++ lib/Apache/Test.pm (working copy) @@ -75,7 +75,7 @@ Test::More->import(@testmore); \&Test::More::plan; - } or die "-withtestmore error: $@"; + } or print "1..0 # skipped: -withtestmore error [EMAIL PROTECTED]" && exit; # clean up arguments to export_to_level shift; of course, that will rely on a recent fix to mod_perl svn :) >> or not worry about it at all - t/more isn't in the MANIFEST, so it >> will only >> be a "problem" for people like us. I mean, we can spend tuits mucking >> around with it, but I don't think it's all that important, since >> -withtestmore is marked as "useful but experimental" anyway. > > > Why not put it in a separate test suite then? That should be an easy > thing to do, and Apache-Test already includes additional test suites > since a few days. sure, that's fine. --Geoff