The end goal here is that Subversion should use Berkeley DB 4.1.24.
Although some people are already doing so, it takes some fiddling to
get it to work with apr-util, because apr-util hasn't yet received the
same adjustments that Subversion got in revision 3467. See this
thread for what happened when I tried to build Subversion (including
mod_dav_svn) against 4.1.24:
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgId=205789
Technically, this is an apr-util bug not a Subversion bug. But
whatever. If we want to see it fixed by when we need it, then we
should schedule it in this issue tracker.
See also issue #957 about improving apr-util's berkeley db4 detection
and then having Subversion rely on apr-util for the information.
Major