I’m amazed that I can’t run Unity on my new case-sensitive install of OSX. I’m assuming this would have also been a problem once my Linux based NFS file server went into production. Which was intended to host my work.
For a guy like me this is a really really big deal. I feel as though my investment in the engine has been nullified. 
I realize this isn’t the answer you’re looking for, but you can use Disk Utility to create a sparseimage that’s not case sensitive and then work in that. It’s plenty fast and practically transparent.
You can then also store that sparseimage on your NFS server and it will work the exact same way.
I /think/ 
Not what I was looking for but a pretty neat idea. My I concern is performance, but it’s an interesting test. I was figuring that my next bet was an external drive. i
If you use FileVault, OSX basically puts your entire home dir into an encrypted sparseimage. I do this on my MB and run Unity that way with no problems at all.
Cool Will games need to also only be able to run on case-insensitive filesystems?
Awesome. So the sparseimage trick works really well. No performance problems at all, and the build works perfectly well outside of the sparseimage.
I think this information should be put someplace more visible so it’s not such a surprise. Better yet, whatever bug there is to not support case-sensitivity should be squashed.
The previous response is not a solution, it is a workaround for the real problem. It cannot be said that OS X is supported if only a subset of installs is actually supported. This issue not only means that the editor cannot run, but the web player plugin suffers a silent-fail fate as well. This is a critical show stopper. Are there any plans to ever address this issue, or is it relegated to the realm of “let the user deal with it”?
All of my publishes run perfectly well on my case-sensitive filesystem. I just have an external volume now that I work out of. In addition to this I imagined that the web stuff would have to operate on a case-sensitive file system as in all likely hood they’ll be served from a linux system.
So just to be clear, it’s apparently only the editor that won’t run on my filesystem… but that is also true for a variety of OSX “native” applications. Sometimes I can’t believe it’s 2009.
That’s still skirting the issue though. That’s like saying, “Oh don’t bother fixing that old leaky roof, I have a perfectly good umbrella right here!”
That’s absolutely not skirting the issue and not the intent of my post. There is a (new at the time) site where you can vote for RFEs, bugfixes, etc etc. That’s where I’ve taken this. I just want to be clear for those who are searching the forum that their publishes will work.