>>>>> "Joe" == Joe Schaefer <[EMAIL PROTECTED]> writes:
Joe> Yes, I think we would actually. Because moving from mp1 Joe> to mp2 always necessitated a webserver change, so you can't Joe> simply mark it as a CPAN upgrade from mp1 and expect some Joe> random mp1 app-server to be happy about the "upgrade". This is also my fundamental complaint. mp2 is a *different* product, because it works with an entirely different *non-dropin-replacement* webserver, Apache2. I can't "upgrade" my mp1 with mp2 because mp2 doesn't play with Apache1, and mp1 doesn't play with Apache2. That's why, for the current toolchain, it must have a different namespace, because it's not an "upgrade". It's a *new product*. And that's why Apache2_2 won't be necessary. If Apache2 becomes Apache3 because they rewrite everything from scratch again, then we release mp3 with Apache3:: prefixes! -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[email protected]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
