Mo DeJong <firstname.lastname@example.org> writes:
> On 5 Mar 2001, Karl Fogel wrote:
> > This sounds like a good idea; will it work like this?:
> > - svn configuration process looks in the svn working copy for the
> > berkeley db sources. If it finds them, it uses them, instead of
> > whatever bdb might happen to be on the system.
> > - If it does not find them, it behaves as it does now.
> > ?,
> > -K
> That is how the current patch works. I toyed with the
> idea of requiring a db dir the the subversion tree,
> but I figured someone might object on the grounds
> that they already have a db version installed.
That's not the grounds on which Karl and I would object to such a
requirement. The fact is that users can't check out db3 from a
public cvs repository. If we were able to display a helpful error
message that said "please get db3 from cvs with this command...",
it wouldn't be a big deal. This is what we currently do if apr isn't
> One thing to note is that I added an error msg
> to the ./autogen.sh script if a db dir could not
> be found. That assumes that the maintainer
> is going to use a db directory from the
> source tree.
This seems to contradict what Karl was requesting; if a db dir
*isn't* found in the tree, this shouldn't be an error. Configure
should search for a system installation as usual.
Received on Sat Oct 21 14:36:25 2006