Now that APR head is reported as version "1.1" our build system considers it
unacceptable. In fact it only allows versions 0.9.(5 to 9) and 1.0(.anything).
People may take our code now and, at a later date, want to build it against a
later but compatible version of APR. So, is there any reason not to expand
this to allow versions 0.9.(>= 5) and 1.(anything) ? That's what this patch does.
- Julian
Accept higher APR version numbers than before, because APR head is already
out of range at 1.1 and there is no reason to prevent people from building
against future compatible versions of APR.
* configure.in
Accept APR and APR-util 0.9.(>= 5) and 1.* instead of 0.9.(5-9) and 1.0.*.
Index: configure.in
===================================================================
--- configure.in (revision 12010)
+++ configure.in (working copy)
@@ -121,10 +121,10 @@ dnl Configure APR, and local Berkeley DB
dnl verify apr version and set apr flags
changequote(<<, >>)
-APR_VER_REGEX="0\.9\.[5-9]"
-APR_VER_REGEX_TOO="1\.0"
-APU_VER_REGEX="0\.9\.[5-9]"
-APU_VER_REGEX_TOO="1\.0"
+APR_VER_REGEX="0\.9\.\([5-9]\|[1-9][0-9]\)"
+APR_VER_REGEX_TOO="1\."
+APU_VER_REGEX="0\.9\.\([5-9]\|[1-9][0-9]\)"
+APU_VER_REGEX_TOO="1\."
changequote([, ])
SVN_LIB_APR($APR_VER_REGEX, $APR_VER_REGEX_TOO)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 24 01:11:18 2004