On Mon, 16 Apr 2007, David James wrote:
> On 4/16/07, David Anderson <firstname.lastname@example.org> wrote:
> >On 4/17/07, Daniel Rall <email@example.com> wrote:
> >> > +1 to require SQLite for all builds rather than producing a neutered
> >> > build which can't access local repositories.
> >> Nice description. ;-) I tend to favor this approach too. However, I
> >> heard discussion in favor of the neutering approach on IRC.
> >What about defaulting to searching for sqlite and requiring it, and
> >having a --without-ra-local (or --without-sqlite, or whatever) to get
> >a 'neutered' build?
> >Although, my own opinion is that I have sqlite on my systems for other
> >requirements anyway, so I wouldn't mind it becoming mandatory.
> That'd be okay with me. I just don't want users to accidentally end up
> with a build that doesn't support creating or accessing local
> repositories. That would be a disaster.
I don't know about "disaster", but making the option explicit
(e.g. failing configure without it) sounds like a reasonable
compromise to me.
> I don't see the "--without-ra-local --without-svnadmin" feature as a
> must-have. Some users might find this feature handy, if they wanted a
> slimmer build, but I couldn't see anyone going this far just to avoid
> installing sqlite
Received on Tue Apr 17 01:40:51 2007
- application/pgp-signature attachment: stored