Please read my proposal carefully. I was not asking for SVN to ignore
the case of files. I asked for an option ("isWindows") (e. g. admin can
set it to true) that makes the SVN command line client apply
OLD->TMP->NEW algorithm instead of OLD->NEW to prevent problems of the
SVN move command used to change case of files. I never asked for SVN
serve to do anything.
Nico Kadel-Garcia schrieb:
> Stuart Celarier wrote:
>
>> Markus, I think your analysis is incomplete. The issue is that the
>> Subversion server must preserve case on filenames. It must do that
>> because clients on any number of different operating systems will use
>> the same Subversion server, and the server cannot honor case for some
>> clients and ignore it for others.
>>
>> I have been programming on Windows operating systems since Windows
>> 2.0, so I am sensitive to the issue. The "ugliness" of the
>> (inconsistent) case insensitivity of Windows file systems is not a
>> deficiency of Subversion. Consider the case where one uses a client
>> on any other operating system to add the files foo.h and foo.H - this
>> is perfectly legitimate. (IIRC, this convention was used in X Windows
>> Systems to distinguish private and public interfaces.) However,
>> because the Windows file systems do not distinguish between these two
>> names, that prevents one from checking out from a folder containing
>> both files. This does not involve renaming files.
>
>
> This sort of problem is why HylaFAX will not compile under Windows or
> at least older versionf of MacOS: the authors used a naming convention
> for files like "regex.h" and "Regex.h" for different include files
> involving regex.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
Received on Thu Jun 1 07:30:05 2006