On Feb 10, 2012, at 11:03 AM, John Floren wrote: > On Fri, Feb 10, 2012 at 8:44 AM, erik quanstrom > <[email protected]> wrote: >>> Mercurial's a good example as it's got a lot of logic in place to >>> deal with all sorts of odd filesystems already. >>> >> >> well if that the case, then its support isn't worth much. >> nix has been dealing with problems due to osx : mangling. >> >> - erik >> > > I think we decided that the : mangling came from a careless copy from > an iso9660 image... but OS X may be responsible for the case-mangling > of Kill and kill.
That's a good example. If you create the repo on a case-sensitive filesystem and add 'Kill' and 'kill' then you'll find that the repo always has that file in it. If you clone the repo to a case insensitive filesystem, you end up with which ever file comes out of the repo last when you do an 'hg up'. Mercurial preserves both, but you may be in trouble is someone on a case insensitive file system makes a commit to 'Kill'. Luckily the history will be there and it's easy to recover. For those using 9vx on OSX: it's really easy to set up your local drive to support a case sensitive file system. Just don't make it the root partition or where /Users resides in case you run any applications out of ~/Applications that come from certain large corporations (aka any that really pushed the Carbon APIs, or applications that originated in Carbon but were only slowly migrated to Cocoa). You can create a case-sensitive disk image, though that has some drawbacks. Partition your drive and then add an entry into /etc/fstab so that it always mounts at a logical place, and not some /Volumes with a potentially variable name. -jas
