[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: Féliciano Matias <feliciano.matias_at_free.fr>
Date: 2002-07-30 14:53:06 CEST

Le mar 30/07/2002 à 13:37, Ben Collins-Sussman a écrit :
> Féliciano Matias <feliciano.matias@free.fr> writes:
> > Everybody know that "file://`pwd`/dir' is equivalent to 'dir'. This is
> > not true with subversion :
> > $ svn co file://`pwd`/repos somewhere # work
> > $ svn co repos somewhere # doesn't work
> > $ svnadmin dump repos > /dev/null # work
> > $ svnadmin dump file://`pwd`/repos > /dev/null # doesn't word
> It may not be clear from the handbook, but there are fundamental
> design points here.

The handbook has been updated and it's quite clear now :

'(Note that the `svnadmin' and `svnlook' programs operate _directly_ on
'a repository, by linking to `libsvn_fs.so'. So these tools expect
'ordinary, local paths to the repositories. This is in contrast with
'the `svn' client program, which always accesses a repository via some
'URL, whether it be via <http://> or <file:///> schemas.)

> 'svnadmin' and 'svnlook' have no concept of networking. They are
> designed to operate directly on repositories. Plain and simple.

My exemple with svnadmin is not very good.

svn claim to understand file:// and use file://.

In svn, file:///var/svn/repos/proj_A/README means :
file proj_A/README of the local repository in /var/svn/repos.
In a browser file:///var/svn/repos/proj_A/README means :
file /var/svn/repos/proj_A/README.

Use of file:// by svn is only to reach a repository Subversion. So why
to use the so common file://.

All URL file:// that can be use by svn can't be used by a browser
(except the repository root and not in the same way that svn).

All URL file:// that can be use by a browse can't be use by svn.

two URL (file://...) and two interpretation.

This is what i don't like.

> 'svn' is designed to use any number of network layers; therefore it
> is defined to always contact a repository via URL. Each network layer
> takes responsibility for for some URL schema. ra_dav handles http://
> and https:// schemas. If somebody wrote ra_ftp, it would handle the
> ftp:// schema. ra_local handles the file:// schema.
> A repository URL consists of two parts: the first part takes you to
> the repository itself, the second part is a path *within* the
> repository. For example,
> http://svn.collab.net/repos/svn/trunk/README
> is ultimately decomposed into
> http://svn.collab.net/repos/svn
> and
> /trunk/README.

I don't have any problem with the http:// subversion use. All programs
that claim to understand http:// can use URL http:// that i use with
svn. A remote repository use http and an extension of http (mod_dav).
But Subversion use file:// for something différent to file:// use by all
other programs.


> This same technique is used to decompose file:// urls.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 14:55:07 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.