It's unheard of that an open source project will be prevented from being released, because the infrastructure doesn't support it. And because a few folks suddenly decided to wear god caps.But in your summary you point out that PAUSE will happily hand out MP2 modules for MP1 installations.
The MP2 team is the one making the decision to ignore the real-world implementation of the distribution infrastructure. The "infrastructure doesn't support it," because you're not playing by the rules of said infrastructure.
On 12/31/04, Stas Bekman wrote:
You want to lock it out from CPAN - lock it out. You will only hurt Perl by doing that. Don't forget to lock out the numerous other packages which live on CPAN with this problem for a long time already. If don't lock those out, you can't lock out modperl2.
I'm just a grunt perl guy out in the cheap seats, but the fact that people are even discussing name-space confusion means there IS name-space confusion.
If a regular CPAN upgrade broke running MP1 installations it would hurt Perl's (and mod_perl's) long-standing reputation of stability.
Finally you don't want to use it - don't use it. It's an open source software, it will succeed or fail by *its own merits* and not because the infrastructure has a long known problem but is not willing to evolve.
But if it stirs up the name-space, it's not on its own.
-- . . . . . . . . . . . . . . . . . . . . . . . . Lon Koenig Consulting [EMAIL PROTECTED] (612) 965-6305 http://www.schnoggo.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
