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

Re: locking a file renders repos unusable with older clients

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-03-28 19:44:49 CEST

Ben Collins-Sussman wrote:
> On Mar 26, 2005, at 11:22 AM, Greg Hudson wrote:
>> On Sat, 2005-03-26 at 09:26, Ben Collins-Sussman wrote:
>>> Any program that links to libsvn_repos 1.2, and then opens a
>>> repository,
>>> will auto-upgrade the repository's 'format' file. This could be an
>>> svn
>>> 1.2 client using file:///, or it could be *any* version of mod_dav_svn
>>> or svnserve that just happens to link to the libsvn 1.2 libraries.
>> Here's an idea I don't think anyone has come up with yet:
>> Disable locking by default in 1.2. Turning on locking implies a format
>> bump.
> After another hour of discussion, cmpilato, fitz and I are in favor of
> this idea.
> What we'd like to see:
> * upgrading to 1.2 libraries doesn't make locking appear, doesn't
> affect existing repositories in any way. Attempts to use locking APIs
> against the repository result in unsupported-feature errors.
> * admin runs 'svnadmin upgrade', which:
> - bumps the repos format number (thus blocking older ra_local
> clients)
> - creates 4 new locking-related hook templates
> * subsequent attempts to use locking APIs against the repository are
> successful; the fs implementations notice that the the format number
> is "high enough", and therefore auto-create the new locking tables
> and/or dirs.

Do new repositories start out at format 3 or 4?

Why not do the table creation at "svnadmin upgrade" time?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 28 19:47:14 2005

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.