On 8/19/05, Evan Stark <EStark@point-inc.com> wrote:
> > It's not a solution at all, because that would mean windows clients can
> > no longer communicate with unix servers and vice versa.
>
> Question I've always wondered, does anyone ever really name two different
> files with the same name but different case? What's the scenario?
I've not ran into that directly, but the situation on windows where
files get funky case issues with CVS (still moving over to SVN).
Basically, someone checks in file "foo.bar", and someone else later
changes it's case to "Foo.Bar", or picked up a patched version of
"Foo.Bar" from another developer, etc.
End result is a file in the WC with a different case than CVS (not
sure how SVN handles this). The file system thinks they're the same,
but some tools (even on windows) really freak out about the case
differences. Short of declaring that all files must be in lower-case
only, not a simple solution on Windows.
I view the case sensitivity/insensitivity mismatch problem as a
limitation of the WC's filesystem. The client libs for svn should
"discover" the issue (try to write the second file, discover that
they've already put one down, and then kick back an error to the user
explaining that the respository isn't compatible with their
filesystem).
Another option would be for the respository to have a property/config
option for markig it as case-insensitive for filenames. Our toolchain
here requires that we use windows, so we're just stuck with it, and I
know a lot of other companies are in the same boat.
-Aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 19 19:09:21 2005