--On Friday, July 16, 2004 5:02 PM +0100 Max Bowsher <[EMAIL PROTECTED]> wrote:
And since svn, apache, etc. would need to manually import the new find_apr.m4 or rewrite their build system to use aclocal to get the new macro, it's not worth making this a default, when doing so sacrifices the guarantee that careless upgraders will be forced to notice this change.
Considering aclocal is part of automake, there's zero chance of httpd or Subversion ever using aclocal.
The point isn't about the system install path, it's about people dropping in a new find_ap{ru}.m4 to projects that already have it without doing any modifications. That is: what is the closest behavior to what we had previously - to me that's clearly a default of '[1 0]'.
I don't believe that we *must* force all APR-using projects to change their m4 invocation because of this. Those that have specific version bindings can call APR_FIND_APR with the 'right' version (i.e. httpd 2.1+) - but most projects so far don't care - 0.9 and 1.0 are mostly API compatible or projects build against both (like Subversion, flood, etc, etc.). I'd expect that might change in APR 2.0, so going beyond [1 0] doesn't make sense. -- justin
