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

RE: Subversion 1.6.0 Release Candidate 3 Released

From: Gleason, Todd <tgleason_at_impac.com>
Date: Mon, 2 Mar 2009 15:37:37 -0800

> -----Original Message-----
> From: Hyrum K. Wright [mailto:hyrum_wright_at_mail.utexas.edu]
> Sent: Monday, March 02, 2009 1:02 PM
> To: Bob Archer
> Cc: dev_at_subversion.tigris.org; subversion-users
> Subject: Re: Subversion 1.6.0 Release Candidate 3 Released
> [ when responding to release announcements, please only include
> users_at_subversion.tigris.org
> in the To: or CC: fields. I'm including dev@ in the CC: for this
> mail so users there will know it has been answered, please remove it
> from subsequent replies. ]
> The Subversion project does not publish binary installers or
> packages. It will be up to the individual package maintainers to
> determine how they choose to include or link SQLite against
> That being said, the developers gone to great lengths in the build
> system to ensure that SQLite can be built as part of Subversion
> proper, or that existing SQLite installations can be used. Packagers
> should choose whatever is suitable for their platform.
> In 1.6, SQLite is used as part of the FSFS backend for rep-sharing,
> and in 1.7 it will be used on the client to store working copy

http://subversion.tigris.org/svn_1.6_releasenotes.html simply reads:

XXX: We now require SQLite for both the server and client.

Obviously the release notes aren't done yet, but I suspect this is why
the question came about. Presumably it isn't actually required for the
1.6 client then?

Personally, I'd really like to know what are going to be the
implications of using SQLite on the client to store metadata, even if
it's not until 1.7.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-03 00:38:49 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.