On Sunday, May 25, 2003, at 10:50 PM, danpat wrote:
> Greetings,
>
> We've come across a situation where someone has managed to create
> filenames in the repository that conflict under a filesystem that
> is *without* case sensitivity. I'm still tracking down the users
> set of actions, but I thought I'd send a quick note here anyway.
>
> The repository looks like this:
>
> /trunk/docs/Document1.doc
> /trunk/docs/Document1.Doc
>
> A checkout to a case sensitive filesystem works just fine, as the
> filenames are different. However, under Win32 (both FAT and NTFS),
> a checkout fails with:
>
> A trunk/docs/Document1.doc
> svn: Can't find an entry
> svn: could not checkout a file
> svn: timestamps_equal_p: `Document1.doc' not under revision control
>
> This can be corrected by renaming one of the files to a
> non-conflicting
> name in the repository.
>
> I'm guessing this is an error that probably *can* be detected more
> gracefully
> than this, and it only needs to get as OS specific as "Does this
> filesystem
> support case sensitivity" ?
>
> I'm not sure what the correct thing to do would be, bombing out due
> to a
> filename
> conflict would be fine, but a more useful error message might be
> helpful
> :)
We actually ran into a similar problem in subversion's own repository
(files with a : in their name don't play nicely with windows). The
consensus was that we can't possibly work around every single weird
limitation of every single file system out there, so we don't try. I
mean it's not like it stops at case sensitivity, there are any number
of other strange requirements on various different platforms (god
forbid we ever port to VMS for example), and personally i think we've
got better things to do than keep up with all of them.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 26 04:55:41 2003