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

Re: Berkeley DB in our source tree?

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2000-08-11 17:32:48 CEST

Greg Stein <gstein@lyra.org> writes:
> > > So, here's my question: should I just import Berkeley DB into our
> > > repository on a vendor branch, or should we simply tell people,
> > > "Install Berkeley DB 3.1.4 before you build Subversion" and stay out
> > > of it? What would folks prefer?

Let's not make a vendor branch; we should include it with dist
tarballs when we release, though.

The reason to make a vendor branch is when we have local modifications
we need to maintain against the vendor. Since we don't have such mods
to APR, we don't keep a vendor branch of APR. But we are using a
modified version of Expat (stripped down, basically), so that's why we
vendor branched it.

autogen.sh should handle Berkeley db the same way it does APR: look
for it, and if not found, tell the user (developer) how to get it.
Received on Sat Oct 21 14:36:06 2006

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

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