On 06/21/2011 09:42 AM, Philip Martin wrote: > "C. Michael Pilato" <cmpil...@collab.net> writes: > >> I'd be interested in knowing why the --db-version parameter was >> dropped. In the absence of a solid reason, I think APR should be >> changed to support as much. > > Probably it's because apr is now modular and BDB support is one of the > things that is loaded dynamically. It's easy enough to reinstate > --db-version, but that doesn't fix Subversion because apr no longer > explicitly links against the BDB library. Subversion's configure fails > its link test with 'undefined reference to db_version'.
Hrm. I seem to recall that it used to be extremely important for Subversion to use the same BDB to which APR was linked. mod_dav_svn used APR's DB support for its activities database, and couldn't deal with having APR's DB being one flavor of BDB while the Subversion repositories which it also needed to read/write needed a different flavor of BDB. Has any of this changed since our move (back in 1.5) away from DB-based activities databases? I mean, could we move BDB detection into Subversion proper and that not be catastrophic? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
