Dave Vasilevsky wrote: > 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.
Dave, there is a problem with this approach (I learned this from ChrisP himself some months ago when I tried such a trick for the siag package that also has the problem of exec.c and Exec.c in the same directory): You cannot be sure that the source tarball is sitting in %p/src, whether you rename it or not. There is the FetchAltDir configuration parameter which allows you to download the tarballs to some other directory. Fink will find it there, but your modified extraction with tar -s in the PatchScript will not find it. BTW, in the new galeon package you say in DescPackaging that some such hack is necessary and done, but I don't see it in the *.info file. > 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. That would be a good thing. > 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. Right now the only possibilities are either: change the tarball in the repository so that the case-insensitivity problem goes away, or: include the files that are not extracted correctly in the *.patch file. -- Martin _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
