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

Re: Renaming files on win32

From: Gili <junk_at_bbs.darktech.org>
Date: 2004-12-21 04:37:55 CET

On Mon, 20 Dec 2004 16:34:55 -0700, Kevin Williams wrote:

>Mark Parker wrote:
>> Apple's HFS is also case-sensitive but case-preserving, if I remember
>> correctly. Seems that Joe Random Luser likes his filenames to be pretty
>> but doesn't like to have to type in caps to open them.
>> (Kinda sucks when you, in your righteous indignation, tear down some OS
>> only to find out that the cool-*bsd-based-os-du-jour works the same way,
>> huh?)
>> Mark
>The trick is getting it to work in a consistent fashion on *all*
>platforms, cool or not. I think that's already been accomplished.

        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.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 21 04:40:23 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.