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


From: Ben Collins-Sussman <sussman_at_newton.ch.collab.net>
Date: 2001-02-09 05:01:23 CET

So, I'm writing a routine which, when given a `file:' URL, splits it
into two paths. One path represents an absolute path to the
repository, and the other path represents a location *in* the
repository's filesystem. This is easy to do -- just involves some
trial-and-error calls to svn_fs_open_berkeley().

BUT: the situation has given Karl another chance to gripe at the fact
that repository and fs path aren't split from the get-go, as they are
in CVS. (This comment is aimed at gstein!)

Here's a weird situation: suppose I specify a checkout of


And suppose that an svn repository (a bunch of berkeley db files)
lives in /usr/local/svn/. But ALSO suppose that another svn repository
lives in /usr/local/foo/bar/ ! Which repository should be used?

You might say, "the shorter repos path should be used, rather than the
deeper one". After all, I *think* that this is what would happen if
you created a <directory> mapping nested within another <directory>
mapping into `httpd.conf', no? The higher-up directory mapping would
always win.

Of course, then, what do you do if you *want* to access the nested
repository? You can't. But it's not a problem if we separate the two
paths from the beginning.

"Doctor, doctor, it hurts when I use URLs!"

You all know the punchline... :-)
Received on Sat Oct 21 14:36:21 2006

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.