# The whitespace in front of @echo MUST be a single tab!
return <<'EOF';
test::
@echo This test suite requires Apache::Test
@echo available from the mod_perl 2.0 sources
@echo or the httpd-test distribution.
EOF
}
What happens to 'make test' in that case? It returns success, right?
What I want to avoid is having these cpan-testers problem reports, which I get regarding the broken test suites, when in fact there are just missing.
If that works, that's pretty neat. So we can have this helper target in ModPerl::MM? So you just say:
*MY::test = \&ModPerl::MM::MY::test?
Actually this is not good, as MM::MY is special. May be we should have ModPerl::MMExtra, with this kind of helper routines in it? So we don't pollute ModPerl::MM?
The other problem with using a core module for that, is that it won't be available for mod_perl 1.0. Should we make it a CPAN module and use CPAN::MakeMaker to wrap it in.
That sounds like a good idea to me. Because I also want to abstract all the mod_perl 1.0 vs. 2.0 detection craft, including env vars and Makefile.PL options into a neat sub, that I can use from my CPAN modules. If all Apache::/ModPerl:: CPAN modules will use it, users will have an identical usage scheme (e.g. the way they tell Makefile.PL, whether they want to build against 1.0 or 2.0, etc).
What do you think?
__________________________________________________________________ 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
