Stas Bekman wrote:
Again, this information could be wrong if you have more than one build of mod_perl under the same perl tree. Consider: you build and install mod_perl.so against a threaded httpd and then you build and install another one against a non-threaded httpd. Apache::Build will report the info about the latest one. This is exactly what happens on my system, where I have both versions built with the same perl.
Maybe this indicates that some of the mod_perl modules shouldn't be installed under site_perl, but somewhere under the apache tree ?
You probably mean the module that contains the build info. It's a good idea, but it'll require messing with @INC, which complicates things.
We discussed this issue already, since Geoff had a similar issue and the solution was to simply use PREFIX for users who require more than one mp2 build under the same perl install. It works perfectly.
All I was saying is that Apache::Build may give the wrong info if the user didn't bother/know better to handle the multiple installs, so using the run-time query is a much more robust method.
__________________________________________________________________ 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
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
