[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Coping with BerkeleyDB Upgrades

From: Rich Shepard <rshepard_at_appl-ecosys.com>
Date: Sun, 30 Aug 2009 15:40:07 -0700 (PDT)

How do you more experienced users of subversion deal with upgrades to BDB?
I don't know what specific version was the most current here when I first
created the repository and started tracking projects, but it is not the
current 4.4.20 that's installed.

   From my previous thread you know that I could not continue committing
changes to the project because the BDB back end changed, so I had to remove
the repository and all references to it in the project directory and start
over. That's certainly not efficient nor desired for projects that might
span several years and multiple distribution, BDB, and Subversion upgrades.
How can I prevent this from happening again?

   Can I build Subversion using data storage other than Berkeley-DB? It would
be nice to be able to use SQLite or a human readable file for the initial
imports and all the diffs.



Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-31 08:10:37 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.