On 6 Mar 2001, Ben Collins-Sussman wrote:
> > 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
> found.
Humm. I was under the impression that neon did not
have a public CVS either, how is this any different?
> > 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.
The configure script does that, I was talking about the
./autogen.sh script. Again, I just added the error
in that case to mimic the way neon was setup.
You could certainly leave the patch to autogen.sh
out if it was a big deal.
Mo DeJong
Red Hat Inc
Received on Sat Oct 21 14:36:25 2006