Only 1 issue still not quite cleared yet. Stas suggested bundling Apache-Test with this release of mp1. I don't see how that could be a bad thing, since getting Apache-Test out there and adopted asap is a good thing. Any strong feelings against it? Otherwise I'd just bundle Apache-Test in the release candidate.
The problem is not about bundling it or not. The problem is about PAUSE. You have to hide these files from the indexer. Otherwise it's possible that when you do:
cpan> install Apache::Test
mod_perl 1 will be installed, or if it's installed already nothing will happen.
The same problem happens with search.cpan.org. It should find the Apache::Test distro, not mp1.
search.cpan.org supports the new META.yaml files, however I don't think PAUSE does that already. Currently the only way to bundle is to put files under /inc or /t, which sucks.
Oy! Yeah, I forgot that issue completely. In that case, why can't we just ship Apache-Test on CPAN (if not there already) and PM_REQUIRE it from mp1 Makefile.PL (a lie, but would automatically pull it in nicely enough for ourselves).
I guess it's fine. Also put it on the Apache/Bundle.pm list. Of course it won't work for those manually downloading and installing it. Hence the idea of the bundling.
I'd rather do something like that instead of risking CPAN pollution.
That's for sure. I've emailed Andreas, asking for an advice but haven't heard from him yet.
And the warning/uninstalling of old Apache::test should be taken care of by Apache::Test's Makefile.PL, right ?
yup. it's only a showstopper if we bundle Apache::Test with mp1.
__________________________________________________________________ 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]
