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

Re: [RFC] Canonical Paths

From: Marcus Comstedt <marcus_at_mc.pp.se>
Date: 2002-08-29 01:34:50 CEST

Philip Martin <philip@codematters.co.uk> writes:

> If you version a file called "." on AmigaOS don't expect the working
> copy to work on Unix. If you version a file called ":" on Unix don't
> expect the working copy to work on a system with ":" as a directory
> separator. Etc., etc.

Well, sharing WC's between architectures wasn't really what I was
concerned about. As long as the repository can be shared, I'm fine
with that.

> We had a file called
> packages/freebsd/subversion/files/patch-build::buildcheck.sh
> which was renamed because it failed to checkout on Win32 systems.

As can be expected. Just as a filename with a greek letter in it
would fail to checkout on a UNIX system using a latin-1 system
locale. It's up to project policy to decide on filenames so that they
can be checked out on the relevant systems.

> I'm not a HTTP/WebDAV expert, but it would not surprise me if
> filenames containing '/' characters are not valid.

Hm, now that I think about it, encoding "/" in filenames as "%2f" might
actully work. The file in question would then have the URL
http://www.example.com/repos/foo/bar/gaz%2fonk. This would be really cool.

> Even if there is a
> valid encoding don't expect the working copy to work on Unix.

As I said, as long as the repository works that's fine. I shouldn't
be able to check out the particular file "gaz/onk" of course (there
should be a test here so I don't accidentally get something in the
directory "gaz" if such a directory exists), but any other file that
has a filename that's valid on UNIX.

  // Marcus

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 29 01:35:44 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.