[TSVN] Re: TSVN 1.1.1 release schedule

> > When do you propose to release TSVN 1.1.1? I would like to check the
UNC
> > access to repositories and make sure that works before this release
if
> > possible.
>
> I was thinking about tomorrow - I've got plenty of time for that on a
> sunday ;)
> But if you want to test it first I can wait. But just out of
curiousity:
> what would we do if the UNC access still doesn't work? The bug is
> clearly in the Subversion API...

I just tested on the nightly, and it doesn't fix it for UNC repos. Issue
2011 was about working copies and I think was happening before was that
a path like
\\blazepoint-sjl\temp\wc was having the double backslash condensed to a
single, so it tried to look for the WC in \blazepoint-sjl\temp\wc. And
that is all they have fixed.

SVN 1.1.0 did support UNC repo access already, but you have to use a
funny URL.

svn ls file:///\blazepoint-sjl/temp/repos

actually works OK in SVN cli, but not in TSVN because we always convert
'\' to '/'. So if SVN can do it, we should be able to as well.

The fix I came up with was in SVNurl::Unescape()

... aaagh. Can't put quoted URLs in my C code because outlook express
strips the quotes off ...

Well, in very bad pseudo code:

if (url starts with file:///\) and (next character != '/' or '\')
then after converting all '\' to '/', convert the first one back again.

so file:///\blazepoint-sjl\temp\repos
would be converted to
file:///\blazepoint-sjl/temp/repos

Excuse the lack of escaped backslashes. OE is too confusing.

It is easy to test this on your own PC by sharing a folder and using the
UNC path to it.

Ideally, SVN should support UNC paths in their native form, but I guess
they didn't think of that when they added fsfs, so it won't make it in
until 1.1.2 at least.

Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Oct 24 14:52:47 2004