Philippe M. Chiasson wrote: [...]
In any case, if we install the headers under the perl tree, shouldn't we copy the apache headers there as well? Perhaps Doug will pop up...You still need to have to install mod_perl.so there (don't have to, but that's where we currently install to), so if you reinstall things by removing the apache tree, you have to reinstall mod_perl anyways.Me thinking that it's nice to have all the headers in the same location (we have the ap_ and apr_ headers there already) and we don't need to mess with Apache2 prefixes here. The potential drawback that I could see is the various packaging approaches which will have to know where apache is installed.
That, and what if apache is upgraded/reinstalled and the content of the destination include directory is whiped+reinstalled ?
Well, in my case, I always do
$> perl Makefile.PL PREFIX=$BASE/mod_perl/1.27/
For example. That way all mod_perl stuff is in its own directory. Not in
the perl tree, not in the apache tree (except for libperl.so).
But I seriously have no idea what's the most common thing for users to
do.
Perhaps mod_perl.so should be installed under the perl tree as well. Don't know if it's a good idea.
If anywhere, I think mod_perl.is better of in apache_dir.
__________________________________________________________________
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]
