Jack Howarth wrote: > That would still be hacking around the problem. We have > to face the fact that MacOS X supports both a case-sensitive > and case-insensitive file system. This means we should have > some mechanism to allow for a Files list with foobar on > case-insensitive and foobar/fooBar on case sensitive. > > I'm not seeing how this idea _wouldn't_ result in non-identical .deb files if we build on two otherwise identical setups: you on a case-insensitive filesystem and me on a case-sensitive file system. We _should_ be able to build the package on either, and install on either, without being able to tell where the thing was built.
I'd propose stashing the upper-cased versions in a separate directory in the .deb file, and then use a PostInstScript to copy them over into %p/bin, based on the results of a test for a case-sensitive file system. By the way, this used not to be an issue because our dpkg just let the last file win on case-insensitive filesystems. Though, to my mind, it might be easier not to do any of this, but instead to have openmpi only install the lower-cased executable names, and then to patch packages that use openmpi's executables to look only for those. > On Sat, Jun 20, 2009 at 07:28:03PM -0300, monipol wrote: > >> On 20/06/2009, at 18:48, Jack Howarth wrote: >> >>> I have been looking at adjusting the openmpi >>> package to allow it to build and install on >>> case-sensitive HFS filesystems. I am stuck on >>> how to properly steer mpiCC into the openmpi-dev >>> Files list without breaking the build on the >>> standard HFS filesystem. Perhaps we need some >>> way of flagging files that only are to be >>> packaged if the filesystem is case sensitive? >>> >> [...] >> >> Any chance upstream might help with that? Have they been contacted? Are >> they willing to fix that? >> >> Any chance of patching the Makefiles so that two files with same case- >> sensitive names are created with two different case-sensitive names, >> such as >> >> bin/mpicc >> bin/mpiCC_uppercase >> >> or something similar? Maybe a (shorter) prefix or suffix, or a different >> hierarchy. Not sure how much breakage that would incur though. In theory >> other Fink packages can be patched to use these prefixed or suffixed file >> names. >> >> >> Cheers, >> >> -- >> monipol >> -- Alexander Hansen Fink User Liaison ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel