Re: rfc: top level 2.0 CPAN modules naming

On Wed, 27 Nov 2002, Stas Bekman wrote:
 
> Doesn't Apache2 subdir solve the problem? All other modules with the 
> same name in 1.0 and 2.0 still have the same name.

sort of.  but the idea was to use the 1.x Apache::Registry with 1.99_xx.
with Apache2.pm in effect, you'd get the new one, not the 1.x one.
in any case, ModPerl::Registry wasn't meant to start naming all modules 
with ModPerl::
 
> If that's the only reason, I'd rather see it reverted to Apache::, 
> people keep on referring to Apache::Registry when they mean 
> ModPerl::Registry and it's very confusing.

at some point that'd be fine.  but again, not related to what CPAN modules 
are named.

i guess there's there's no reason to wait on changing the name, tho it 
would be interesting to see 1.x Apache::Registry vs. ModPerl::Registry and 
tune it before making the switch.