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

Re: file:// -> svn://

From: Dave Cridland <dave_at_cridland.net>
Date: 2002-07-31 15:50:09 CEST

On Wed, 2002-07-31 at 14:20, Féliciano Matias wrote:
> Le mer 31/07/2002 à 14:20, Dave Cridland a écrit :


> > Obviously this requires either some backwards compatibility - this would
> > prevent, in this case, "!svn" from being a path component within the
> > repository - or we hold our breath and change it anyway, on the basis
> > that current users should be reading the list.
> >
> > I prefer backwards compatibility as a short-term measure, with the
> > clients emitting a warning about outdated URLs.
> >
> Sorry for my poor english.
> I have no problem with backwards compatibility. But i don't like
> backwards compatibility for a long time, especially in alpha stage.
> Honestly you give a good andwers to a sort of bad question.
> 1 - svn is curently not widely use (normal).
> 2 - svn should be widely use in one or two years (new users).
> We need to give an answers to audience 2 and not to 1 (sorry :o) ).
> It seems than audience 2 (feetback of new users) have some confusing
> with the use of file:// by svn and prefer something like
> svn_local://... .
> So in two years we have 90% of svn_local:// usage and only 10% of
> file:// usage (perhaps i'm wrong !) .
> Should we maintain such "ugly" things like "file://.../!svn/..." only
> for 10% of users ?
> Should we push something that split the subversion communauty ?
> Should we encourage "flame wars" ? (like this reply)
> Perhaps this is the open-source touch :) .

I think you've (almost) completely missed the point, so I obviously put
it badly.

An example:

Repository accessed locally, present in /var/lib/svn/
Node within the repository, called /some/file

(1) Current URL: file:///var/lib/svn/some/file
 - As you state, this is not a "file" scheme, really, since
/var/lib/svn/some/file does not exist.

(2) "Your" URL: svnlocal:///var/lib/svn/some/file
 - This is an entirely new scheme, and thus avoids the "file" issue.

(3) "My" URL: file:///var/lib/svn/!svn/some/file
 - In my proposal, I suggest we create a directory on the host
filesystem - /var/lib/svn/!svn/ - which contains current versions of the
files. So this *is* now a "file" scheme, since
/var/lib/svn/!svn/some/file now exists.

My comments about backward compatibility were about whether to still try
and parse (1) URLs.

Does this make more sense?

[Rest snipped]


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 31 15:47:30 2002

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.