>Unfortunately if Subversion is going to be useful on Windows it is going
>to have to play nicely with case-insensitivity and other file system
>restrictions. Not only Windows; almost every platform has some different
>file naming restrictions. I think Subversion will need, to some extent,
>generalised support for file system restrictions:
I agree with this. This discussion so far kind of reminds me of cvs and
binary files ("it's too hard to do right", "the user should have to specify
that and it shouldn't be automatic", etc.). SVN was right to handle binary
files transparently, and the "you don't need that" attitude was wrong,
especially when it came to costing the user time and potentially data. If
there's a possibility of getting screwed up and losing a weekend to a
problem (like what happened here), then the tool should handle it. Better
to spend a week implementing a feature in the tool than to spend #users * a
weekend for all eternity.
At the very least, svn should know what's going wrong (the files in the
repository would be the same on the OS that's currently co/up'ing) and tell
the user (and then they can rename through the URL interface). Randomly
failing is wrong. It's not that hard to spec out the currently supported
filesystems and what their constraints are, and require somebody to do that
for any port target for svn. There should be a spec for what the
repository stores as well (I assume it follows url rules, which is fine).
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 30 08:51:20 2003