[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: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: 2007-11-19 22:44:34 CET

David Glasser wrote:
> 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.
>
> This is our current INSTALL section:
>
>
> 3. SQLite 3.x or newer (REQUIRED for client and server)
>
> SQLite is a lightweight, embeddable SQL library necessary to
> build any repository-related code.
>
> You can get sqlite 3.5.2 from:
>
> http://www.sqlite.org/sqlite-3.5.2.tar.gz
>
> You can build and install sqlite however you wish. However,
> you also have the option of unpacking the archive into the
> top of the Subversion source tree and renaming the resulting
> directory within the Subversion source code) from
> ./sqlite-3.5.2/ to ./sqlite/. Subversion will then build
> and install it for you.
>
> 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?

My Ubuntu Gutsy install is running 3.4.2. 3.3.9 was released on Jan 4,
2007. My feeling is that most distributions will be shipping at least
3.3.9 (and probably some variant of 3.4 or 3.5) by the time they are
also including Subversion 1.5.

> ... 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.
>
> --dave
>

Received on Mon Nov 19 22:45:09 2007

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