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

Re: svn commit: r27922 - in trunk: . subversion/include subversion/libsvn_fs_util

From: David Glasser <glasser_at_davidglasser.net>
Date: 2007-11-20 18:04:04 CET

On Nov 20, 2007 9:46 AM, Philip Martin <philip@codematters.co.uk> wrote:
> "David Glasser" <glasser@davidglasser.net> writes:
>
> > On Nov 19, 2007 2:30 PM, <glasser@tigris.org> wrote:
> >
> >> In order to do this, we add a few new helper macros, and make sure to
> >> always use sqlite3_prepare_v2 instead of sqlite3_prepare; the "v2"
> >> version returns the precise error code from sqlite3_step instead of
> >> just returning SQLITE3_ERROR.
> >
> > This seems to require SQLite 3.3.9.
>
> > We are already using an AUTOVACUUM feature that requires 3.1.
> >
> > Do we know what the status of sqlite3 versions on various popular
> > Linux packagers is?
>
> Debian Etch (the stable distribution) comes with 3.3.8, so Subversion
> no longer builds on my machine :(

Out of curiosity, is the Etch sqlite threadsafe? ie

#include <sqlite3.h>

int main(int argc,char** argv) { printf("%d\n", sqlite3_threadsafe()); }

> > ... alternatively, we *could* just ship svn with the single-file
> > (sqlite3.c/sqlite3.h) copy of the latest version of sqlite, and avoid
> > making anybody ever have to deal with installing it. Given how much
> > of a dependency-hog we already are, I'd kind of like this route.
>
> Distributions will probably want to build against a system sqlite as
> an embedded version makes security support harder.

Yeah, that is probably true.

--dave

-- 
David Glasser | glasser_at_davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 20 18:08:41 2007

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.