Philippe M. Chiasson wrote:
On Thu, 2003-01-30 at 12:32, Stas Bekman wrote:The attached patch (because it has \t embedded) enables the installation of src/modules/perl/*.h and xs/*.h files, because we need them to be installed for XS extensions to be built.
+1 Great!First of all I'm not sure if that's the right way to install these, but it works for me.
Second, I've chosen to install them to $APACHE_INSTALL_DIR/include in parallel with $APACHE_INSTALL_DIR/modules where we install mod_perl.so to. Is this a good choice, or do we want to install it under the perl lib tree as in mod_perl 1.0?
I would rather see it installed in the perl tree, just like in 1.0.
I'm +0 on any place, it just was easier for me to implement it that way ;)
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 ?
Perhaps mod_perl.so should be installed under the perl tree as well. Don't know if it's a good idea.
__________________________________________________________________
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]
