Frederic LE GUERN wrote: [...]
As far as I can see DESTDIR's becoming pretty standard and it is available
in Apache's Makefile so I wouldn't call it a perl thingy anymore...
It may be called the same way, but it's easy to see that it's not the same thing.
Yet I understand your point as we have two packages here ; once again, the question is, does it make sense to build a separate package for mod_perl or should we (can we btw?) always build both mod_perl *and* apache at the same time ? My answer is still not for me...
If you build a static Apache/mod_perl then you have no choice.
If you build a DSO mod_perl, then you need to have apache built and installed already. if you had the apache installed in DESTDIR, then yes, DESTDIR would work across all, but this is not the case.
That's why the only sensible thing I can suggest is a second DESTDIR argument, which is apache-specific and of course it needs to be called differently. I've earlier suggested MP_AP_DESTDIR.
-- __________________________________________________________________ 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
