This is probably because HFS+ (the default file system for OS X) is case-preserving, but not case-sensitive. This means that filenames that differ only in capitalization are considered to be the same. Although this works on Linux, it is poor practice to name files this way, not only because developers can easily confuse the files, but also because it causes such issues with non-case-sensitive filesystems. Your best bet is to remove all such near-identical filenames by renaming one of the pair, and slap the developers who named the files that way on the wrist. :-) (Then explain why it's a bad idea.)
- Quinn On Jan 4, 2010, at 1:41 AM, Jason wrote: > Hey, > > I have a problem and have diagnosed it as a name conflict. However, > this appears to be working fine for the developers that use Linux. The > problem is as follows. There are a number of instances in the > application where there are near identical filenames. For example. > > swfupload.js > Swfupload.js > > verdana.swf > Verdana.swf > > When versions hits these files it throws a wobbly, says it cannot > write file and stops the export. If I try to run the update afterwards > it says that the file is locked. Is there a setting to overcome this > issue? > > -- > > You received this message because you are subscribed to the Google Groups > "Versions" group. > To post to this group, send email to versi...@googlegroups.com. > To unsubscribe from this group, send email to > versions+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/versions?hl=en. > >
smime.p7s
Description: S/MIME cryptographic signature
