Gili wrote:
> I think in the end you will have to always store
> case-sensitivity on the server but use OS-specific behavior on the
> client end. There is absolutely no magic way you will be able to deal
> with someone on unix storing two different files "abc" and "Abc" and
> someone on windows trying to check them out. The best the client can do
> is warn unix commiters of this causing problems for win32 clients, at
> commit time; and warn win32 users at checkout time that there exist two
> different files that resolve to the same canonical filename on
> checkout. Java handles this problem pretty well on a conceptual level.
> Files have normal filenames and canonical filenames. If your
> file-system is case-aware then variations of the filename casing will
> always resolve to the same canonical filename -- hence you do filename
> comparison and "file already exists" checks against the canonical
> filenames instead of the original ones.
You miss something. If I specify the file "abc" in my source code for
include (or something similar), it will work on Windows even if the file
is named "AbC", but no longer on a Linux machine. This would make
cross-platform developing much more difficult than now.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 22 22:48:20 2004