On Jul 28, 2006, at 6:26 PM, Lars Rosengreen wrote: > Please excuse me for continuing a discussion that is several months > old, but I am still not sure about a few things. > > On 1/11/06, David R. Morrison <[EMAIL PROTECTED]> wrote: >> >> On Jan 10, 2006, at 10:05 PM, Lars Rosengreen wrote: >> >> > On 1/10/06, David R. Morrison <[EMAIL PROTECTED]> wrote:
>> There are two ways to handle packages which need differences for the >> powerpc and i386 architectures. One way is to use the existing >> variants mechanism: we already have %m which fink will automatically >> resolve to either powerpc or i386, so you can use constructions like >> >> (%m = powerpc) foo >> (%m = i386) bar >> >> The other way is to use separate .info files for powerpc and i366 >> architectures. Each of the separate files should have the new >> Architecture field which designates which architecture the package is >> designed for. The names of the files should be %n-%m.info (e.g., >> foo- >> powerpc.info and foo-i386.info) or %n-%m-%v-%r.info (e.g. foo- >> powerpc-1.1-1.info and foo-i386-1.1-1.info). > > I have a package "sbcl" that I have split into two .info files, one > for each arch --> sbcl-i386.info and sbcl-powerpc.info (variants won't > work in this specific case). What should the Package: field be for > both of these files? The Package field is sbcl for both packages. You need an Architecture field for each one, and the names of the files should be sbcl-powerpc.info and sbcl-i386.info. > On a sort of related note, another common lisp implementation I > maintain now has a 64bit G5 specific version in addition to the > original generic powerpc version. What can I do to ensure that only > someone with a G5 installs the G5 version? Is there a virtual package > or something I can depend on? What do you mean by a 64bit version? Is this a version with 64bit libraries and 64bit executables? (You can determine this by using / usr/bin/file, or attempting to run otool on the files, which won't work for 64bit files -- there is a corresponding otool64 for them.) 64bit libraries cannot be mixed and matched with 32bit libraries, and the tentative decision for fink is to use %p/lib64 instead of %p/lib for these libraries. There is only one package at the moment which builds 64bit libraries, gmp-64bit, which you could use as a guide. Some of its features were described in an aerlier post to fink-devel: http://article.gmane.org/gmane.os.apple.fink.devel/13045 -- Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
