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

RE: Status of 1.6

From: Bert Huijben <rhuijben_at_sharpsvn.net>
Date: Tue, 6 Jan 2009 23:34:39 +0100

> -----Original Message-----
> From: justin.erenkrantz_at_gmail.com [mailto:justin.erenkrantz_at_gmail.com]
> On Behalf Of Justin Erenkrantz
> Sent: Tuesday, January 06, 2009 6:35 PM
> To: Hyrum K. Wright
> Cc: Mark Phippard; dev_at_subversion.tigris.org; Julian Foad; Senthil
> Kumaran S
> Subject: Re: Status of 1.6
> On Tue, Jan 6, 2009 at 7:53 AM, Hyrum K. Wright
> <hyrum_wright_at_mail.utexas.edu> wrote:
> > As far as requiring "such a recent version" of SQLite, we currently
> require
> > 3.4.0 or above, which was released on June 18, 2007. I'm of the
> opinion that if
> > a user wants to install a new version of Subversion, they may have to
> install
> > newer versions of the dependencies. Hopefully packagers are
> sensitive to this
> > fact as well, and will provide ways to get those dependencies.
> +1.
> I did the work to make OS X 10.5's bundled copy of SQLite (3.4.0)
> happy. Others who want to push the dependency back even further for
> their favorite OS can submit patches too... -- justin

Just making subversion happy to use older Sqlite versions may introduce
working copy incompatibilities if you share working copies between different
clients (and sometimes OSs). The Sqlite database format is part of the
repository format and will be part of the subversion working copy format.
And if different binary packagers choose different versions we may introduce
extra incompatibilities later.

3.6 still defaults to the 3.0 compatible database format, but it does have
support for a later format.

On my primary development OS, I use at least three binary distributions next
to each other which all compile their own depencies. (TortoiseSVN, AnkhSVN
and a commandline client). In my very specific case I'm responsible for
compiling two out of these three, but I can imagine cases where many more
binaries are used next to each other by users who control none; especially
using some of the commercial subversion clients on Windows and OS X.

I would prefer to limit the amount of supported sqlite releases per
subversion release (Maybe 3.4+ for 1.6 and 3.5+ for 1.8, etc.) to make sure
working copies for a single version are always compatible. Using the
amalgamation version of sqlite in our release would make sure we always have
a compatible working copy/repository format.


Received on 2009-01-07 08:54:28 CET

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