Re: MP_APXS vs MP_AP_PREFIX

[Geoffrey Young]

optional both at mod_perl build time and an 3rd party module build 
time? I'd like to think that we can make this work so that mod_perl 
does the right thing - if mod_perl was built with the md5 versioning, 
then WriteMakefile does the right thing (or as close as we can get).


You forget that you need to pass the locaion of httpd so it'll choose 
the right md5sum. Otherwise it's a chiken and an egg problem.
hmph.  I don't see an easy way for mod_perl to intuit the location of httpd 
at build time.  if we have MP_APXS then we're ok, but the user might be 
building from a source directory and have httpd someplace like /opt.

Users should have an exact same behavior as it is now. Only if the 
special mode is used, and a path to httpd is passed and there is a 
matching md5sum, then use the other config.

how about MP_VERSIONED_BUILD=1 for the mod_perl end?


+0. I'd stick to MP_MAINTAINER=1 and only add new features if we really 
have a need for it. So far I don't see normal users installing 2.1 on 
their machines along with 2.0. We can always add it later if the need 
arises.
ok.  but remember it's not just 2.0 versus 2.1 - it can also be 2.0 with 
multiple mpms.  granted, using a different mpm isn't likely to cause 
compilation errors later on...

hmm.

if mpms won't cause compile problems, I wonder if just specifying the apache 
version is enough.  so, instead of having an md5 hash against the path to 
httpd, we just did Apache::BuildConf-2_0_48  (or maybe 
Apache::BuildConf::2_0_48).  it still means that you could have multiple 
versions of 2.0.48 with different compile-time settings and you'd get the 
wrong build options, but typically with third-party installs you're only 
interested in the location of the header files and other minor stuff like 
platform...

--Geoff

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]