On Thu, 31 Jan 2002 11:52:27 -0600, Doug Rowland wrote:
> I was trying to install the pygtk package on OS X 10.1.2 on an HFS > filesystem and there is a problem with the case-insensitivity. In > particular, there are two files GTK.py and gtk.py which are distinct but > HFS overwrites gtk.py with GTK.py when it extracts the files from the > tarball. > > To get around this, you can extract the tarball, then > mv GTK.py GTK_HFS.py > > extract just gtk.py from the tarball, then edit it by changing > import GTK.py * > to import GTK_HFS.py * (near the top of the file) > > In my limited testing that seemed to make the two pygtk programs I tried > work just fine (as long as they don't separately import GTK.py, in which > case you'd have to edit those files too). > > Is there a better way to get around this? There are a few options: 1) What you did, extract any duplicates one by one and then manually edit any files that refer to them. A variant of this is to rename the duplicates, create a new repackaged tarball with these files renamed, and then have that put up on the net as the source package. This simplifies the .info file at the price of having to bug an admin every time you need a repackaged tarball uploaded. 2) The version of tar that comes with OS X (/usr/bin/tar) has a -s option that allows you to automatically rename files as they are being extracted from the tarball. Also, if there are a lot of files that refer to one of the duplicates you're renaming, you can use sed to find-and-replace on the name of the file instead of doing it in one big patch file. This makes the .info file look fairly complicated, but since most issues are being handled automatically it makes switching versions easier. See the Galeon and mpg123 packages for examples of this approach. 3) There's some code sitting in the patch tracker for a new field in Fink, TarFilesRename:, that will semi-automatically do the whole renaming bit. I don't know if and when the patch actually will go into the Fink codebase though. And you'll still need to deal with references to the file on your own, either with a patch or sed. > Does everyone else except me use UFS? What are the pros/cons to UFS > relative to HFS? I suppose UFS works fine as long as all you're working with is unix software such as that provided by Fink. But several features of OS X--and all of Classic--apparently break when used on UFS. So I think most of us stick with HFS+. Dave _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
