> asinine case-sensitivity .... moronic behavior.

You're entitled to your opinion, of course (and I'm sure that came across more strongly than you intended). But as you say (I think), Subversion really has no choice but to be case sensitive since there will be people with case-sensitive data to store in it.

Still, it is primarily FoxPro that is being moronic. I use VS.NET on Windows with subversion and have never had a problem involving file names changing. I also check in wordprocessing documents, they're fine.

I don't disagree that Subversion could improve regarding case. In fact having a property, perhaps "svn:ignore-case" you could set on a directory would be brilliant. The topic is more complex than I suspect you imagine - be sure, subversion is VERY carefully thought out and if there was an easy solution they'd have done it by now. And they do occasionally reverse 'over my dead body' stances too (eg the ".svn" VS.NET web project problem)

There are several workarounds for the case problem, ranging from Dragan's little snippet to pre-commit scripts.

But for me, the killer is this : why do you want Subversion anyway, is it because you just want a "safer SourceSafe", or because you want to use what Subversion can give you - effective diffs, multi-branch, merging etc, externals, pretty web interface. Because if you just want a safe place to put SCX and VCX files, try a backup program <g>

I get the feeling all most people want is an SCC interface for Subversion, so they can use it inside the FoxPro IDE as if it was Sourcesafe, only safer. If that's the case, go for an SCC interface for subversion .. which is not where this thread is going.