Mac OS X has a case insensitive, case preserving filesystem. Trying to checkout gentoo-x86 module on such a filesystem causes cvs to abort client-side because of two directories:
The trick is to checkout CVS inside a case-sensitive filesystem image:
hdiutil create -fs UFS -volname my-cvs -verbose -size 512M chroot
Make sure to point your /usr/portage/distfiles directory to a location on the case-sensitive filesystem to detect problems with distfile naming stuff.
There might be a way to resolve this problem and make our cvs repository safe for use on a case insensitive filesystem by creating a virtual/cvs and have it point to dev-util/cvs-tool (renamed 'cvs')
ciaranm: what do you think about the last suggestion on renaming dev-util/cvs?
I think it's a bad idea. You have an option for a sane file system on osx, right?
We do have case-sensitive filesystem options on Mac OS X, mounting a separate filestysem image and using that for CVS.
I think most of the ppc-macos devs use a non-ppc-macos box for cvs anyhow (as was suggested).
I just wanted to add that, in MacOSX Panther (10.3) you have the option of making HFS+ partitions case sensitive.
This is possible in gui on OSX Server. For OSX Client you need fingers, too:
newfs_hfs -v "Volume Name" -J -s /dev/devicename
You can lookup device name by various means, eg Disk Utility.app.
Be sure to umount the device before formatting ;)
I didn't test, but HFS+ case sensitive appears to work on MacOSX Jaguar (10.2) too, you just need to copy over the `new_hfs' binary.
A word of warning, it breaks *some* MacOSX applications, eg:
I got it running without troubles on my machines, just a really few apps have this problem.
I think this solution is cleaner than having a separate disk (well, you can still have a separate disk image and use HFS+ instead of UFS then :).
Also, you need to format your partitions to take advantage of it ...
Closing out bugs that've been resolved for a while now...