Though I want to have the issue with bundling and dual-life CPAN packages settled down first, before we can release Apache::Test separately. Since it may cause mod_perl 2.0 installation when Apache::Test is requested (however it's actually not a problem now, since mod_perl 2.0 is really hidden.) So I guess that this is not a showstopper.
> that way we can say "to use $x feature you need mod_perl 1.99_9 or > Apache::Test 1.0." basically, 2.0 modules could then PREREQ_PM 1.99_09 > and 1.0 modules could PREREQ_PM Apache::Test 1.0 but both would get the > same feature support.
I doubt this will work. Since _09 prevents from CPAN to see mod_perl 2.0.
__________________________________________________________________ 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]
