You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by William Uther <wi...@cs.cmu.edu> on 2002/06/06 19:11:36 UTC
Case Sensitivity (was: Re: A List of Issues)
On 6/6/02 1:37 AM, "Bill Tutt" <ra...@lyra.org> wrote:
> Err.. Sorry 'bout that, Jay's real comment about case sensitivity was so
> far down in his email I missed what he was talking about. My
> apologies...
>
> Path/File canonicalizing should lookup the files actual case and pass
> that into libsvn_client.
I don't think this is quite enough (close, but not quite). It handles all
the cases where the user is passing filenames to the client. It doesn't
handle cases where the server is passing filenames to the working copy.
There are a few examples where it is a problem:
- Checking out (or an update which adds) two files whose filenames only
differ in case. It should probably cause an error, but if I understand the
current libraries/interfaces correctly then checks for this sort of thing
need to be in more than just the client. It is a general working copy
problem. This generalizes to needing to detect obstructions caused by case
aliasing (e.g. An update wants to add a file that already exists but only
with different case).
- The ability to rename a file to a different case needs to exist (issue
667).
Later,
\x/ill :-}
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Case Sensitivity (was: Re: A List of Issues)
Posted by Wade Williams <wa...@mac.com>.
On Friday, June 7, 2002, at 05:23 AM, brane@xbc.nu wrote:
> Quoting Philip Martin <ph...@codematters.co.uk>:
>
>> Another problem is filenames containing "special" characters. On Unix
>> filenames containing ':' and '\' are perfectly reasonable. Subversion
>> had a file with a ':' in it's name at one point (see the log for revs
>> 1795 and 1805). That caused the Windows svn client to complain but was
>> fine on Unix. I suspect that a filename containing '\' would also
>> cause problems.
>
Can I add in a couple of things to consider on case sensitivity?
1) If subversion is to run on MacOS X, it should be noted that the
default file system HFS+, is case-preserving but not case-sensitive.
This causes problems with some Unix programs that use MAKEFILE and
Makefile for example. However, there's no good reason for having files
identical in name, which differ only in case.
I think this will change later as I highly suspect Apple is working on a
new file system, but for compatibility reasons, HFS+ will be around for
years to come.
2) The colon ":" is a special character on Macintosh systems.
Wade
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Case Sensitivity (was: Re: A List of Issues)
Posted by br...@xbc.nu.
Quoting Philip Martin <ph...@codematters.co.uk>:
> Another problem is filenames containing "special" characters. On Unix
> filenames containing ':' and '\' are perfectly reasonable. Subversion
> had a file with a ':' in it's name at one point (see the log for revs
> 1795 and 1805). That caused the Windows svn client to complain but was
> fine on Unix. I suspect that a filename containing '\' would also
> cause problems.
I don't think it would be wise to add special checks for such characters to the
libraries. A checkout would fail anyway. IMHO file naming is a matter of project
policy. If people want to make sure their reporitory contains no "bad" file
names, they can write a pre-commit hook script to check that.
(Having an example of such a script in contrib/ wouldn't hurt, of course.)
Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Case Sensitivity (was: Re: A List of Issues)
Posted by Philip Martin <ph...@codematters.co.uk>.
William Uther <wi...@cs.cmu.edu> writes:
> It doesn't
> handle cases where the server is passing filenames to the working copy.
>
> There are a few examples where it is a problem:
>
> - Checking out (or an update which adds) two files whose filenames only
> differ in case. It should probably cause an error, but if I understand the
> current libraries/interfaces correctly then checks for this sort of thing
> need to be in more than just the client. It is a general working copy
> problem. This generalizes to needing to detect obstructions caused by case
> aliasing (e.g. An update wants to add a file that already exists but only
> with different case).
>
> - The ability to rename a file to a different case needs to exist (issue
> 667).
Another problem is filenames containing "special" characters. On Unix
filenames containing ':' and '\' are perfectly reasonable. Subversion
had a file with a ':' in it's name at one point (see the log for revs
1795 and 1805). That caused the Windows svn client to complain but was
fine on Unix. I suspect that a filename containing '\' would also
cause problems.
--
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org