site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=alastairs-place.net; h= subject:mime-version:content-type:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; q=dns/txt; s= aug07; bh=ahjbMSJostiNDqLbs966+Dztgmw=; b=vRLe+HW3gh2y5mHQTkNesE vCDsoD5YCCJ8BBfW7o7iX1dlP3WthZujlHGrKxW2QTGlTBh70bVYrkNyrvYk6+Il uiYAARa8xOVUBhrLT97+w68AfxNDf17039TzIlbCbq9gjQdpQgIJFb/AWdLL1DEP obzJyucqG5uS03/kwlVDE= On 7 Oct 2009, at 18:09, Allen Curtis wrote: On 6 Oct 2009, at 20:08, Jamison Hope wrote: Kind regards, Alastair. -- http://alastairs-place.net _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Use a case sensitive file system. Have a disk partition formatted as UFS, or a UFS-formatted disk image and do your svn checkout there. I don't think Disk Utility can create a UFS disk image, but hdiutil can. http://codesnippets.joyent.com/posts/show/2084 I'd strongly recommend against using UFS, actually. Case-sensitive HFS+ is a much better option. Well, I am still a little confused about which is case-sensitive vs. case-preserving. In my case, it must be case-sensitive. Case-sensitive means that FOOBAR.C is a different file from foobar.c and from FooBar.C and so on. Case-sensitive filesystems are generally case-preserving (though there are implementations of FAT that are non- case-preserving but that are nevertheless case-sensitive... yes, this is stupid, before you ask). Case-preserving means that FOOBAR.C, foobar.c and FooBar.C are all the same file, *but* that you'll always see the filename *as you saved it*... so if you save it as "fOObAR.c", then that's what you'll see in a directory listing, even if you then open it up as "FOOBAR.C" (for instance). Case-preserving is what FAT32, VFAT, NTFS (except when accessed from the POSIX subsystem, at which point it behaves case-sensitively [yes, really... and yes, that can cause havoc for Windows native software]) and standard HFS+ do. HFS+, however, has an option to be case- sensitive, and you can format such a filesystem with Disk Utility or third-party software such as (shameless plug) iPartition. There are systems that are neither case-sensitive nor case-preserving (various implementations of FAT are like this, for example), so when you save "FOOBAR.C", "foobar.c", "FooBar.C" or whatever, you'll get either "FOOBAR.C" or "foobar.c" depending on the preference of the filesystem's developer. BTW: This will be a problem for any Linux kernel developer wishing to use their Mac for development. The problem is the stupid decision on the part of the Linux kernel people to have filenames that differ only by case in their source tree. In the meantime, you can create a case-sensitive HFS+ filesystem somewhere (e.g. in a disk image, in another partition, on an external disk, or mounted over the network) where you'll get the behaviour you want. This email sent to site_archiver@lists.apple.com