von Löwis Martin wrote:
> > Deal with it how? If there is a file that fails on Windows,
> > what should it do? Somehow rename that file? What about the
> > case of two files: "More" and "More..." which end up being
> > collapsed onto each other on the Windows platform? (Or
> > "more" and "More")
>
> It should use the value of the svn:filename.win32 property
> (if specified). If you want to have both "More" and
> "More..." in a directory, you should set svn:filename.win32
> to "More-trailingdots", or "More\u2026". The working copy
> should maintain the repository name and the disk name of
> the file.
Wouldn't it be much, much simpler if Subversion just didn't check the files out?
Seems like the implementation is OK straight forward.
Other than the implementation, it's just a policy change, right?
The rules are simple too. When checking out files on Windows:
- Skip files ending in trailing dots
- Skip files with names containing \ / : * ? " < > |
- Skip files whose name clashes on a case insensitive filesystem
(just skip both/all files to avoid any mistakes).
It could be done server side or client side, which is best?
Performance is not an issue for the first two cases. For the last
case someone will have to do a bit of thinking to find the most
performance optimal way. I imagine you could just use an efficient
sorting algorithm to sort all the filenames in a given directory
(someone must've done this efficiently before), then just strcmp()
each filename with the next in the sorted list.
I agree that Subversion doesn't handle this very well.
The "clashing filenames" problem shows up on the TSVN mailing list quite often.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 6 18:39:36 2006