No, I understand it now. I think the unique value you are after is the path to httpd, including httpd (for those distros moving it to /usr/bin).
Though you are going to have a hard time maintaining several configs in one file. Instead it's probably better to abstract those into separate files, so when you add a new build you don't need to update that file but only install new build. I was thinking to use an approach taken by Inline, when it builds the shared library. It uses an MD5 hash of the C source as a part of the filename. So when the source changes it knows to rebuild it. We could take an MD5 hash of the path to httpd. Then create:
BuildConfig-16128e67ad092a739842b82295820e31.pm BuildConfig-938883be41ad5efc6c9c0d7affdae8e9.pm
where the hash is httpd run through md5? sick.
I like it :)
for each build (2 builds above).
Next, when Apache::BuildConfig loads, it could optionally get the http argument, calculate its md5 hash and pick the right BuildConfig file above.
We also need:
BuildConfig-default.pm
which will store the first build, in case the path to httpd is not passed (that's what most users will want: "just use my mp2 build data".
what might work is installing both BuildConfig.pm and BuildConfig-$hash.pm. BuildConfig would work as it does presently (containing the most-recent install data) and would be there for back compat (new WriteMakefile vs old mod_perl).
The problem is that MD5 modules aren't in the core.
they are in 5.8.0. not sure about 5.6.x. but I thought we made the decision to move to 5.8.0 once 5.8.1 came out. I can't remember, though.
But 99.9999% of users won't need this feature, so if we can make it optional (or e.g. when MP_MAINTAINER is on).
I agree, most people won't care about this, so making it optional at build time is best.
may be keeping Apache::BuildConfig as it is now, but instrument it to optionally check for these special files, which will be useful for developers.
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).
how about MP_VERSIONED_BUILD=1 for the mod_perl end?
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
