> 1) expecting people to not have modperl1 for a significant time > following the modperl2 release, like everyone would "upgrade > tomorrow" thus trivializing the overlap issue.
I don't see how there's more of an overlap issue with mod_perl than any other module. What do I do when I want to run two versions of Class::DBI or XML::LibXML? I install two perls. This happens all the time. Despite the lip service paid to backwards compatibility, module APIs do change over time, and running multiple perl installations handles this issue. I'm not wild about the "use Apache2" solution either, but I just don't use it. Wouldn't it be easier to add a big warning about mod_perl 1 compatibility to the install and provide a short document describing how to run multiple perl installations than to try and change all this infrastructure? - Perrin -- 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
