Should probably try to make it mod_perl2.c too, then - the whole point of php using the major version number in the .so file is that you can load multiple versions into the same server. While it's true that that's not applicable for mp1/mp2, if it's compiled as mod_perl.c, I'm not sure if Apache will ever let 2 different versions of the module into the server. This is either desirable or not. If it is, I believe we need to change the .c reference too. If not, there's no reason to do mod_perl2.so
Good point, Issac. We shouldn't change something just because we can.
So I withdraw my proposal, unless you can see another compelling reason I haven't thought of.
p.s. that reason would be for example distro's installing mod_perl.so into a global area like /usr/lib. But in this case they will need to do the same for mod_include, mod_proxy and all other Apache2 modules...
__________________________________________________________________ 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]
