On 7/29/06, David R. Morrison <[EMAIL PROTECTED]> wrote: > > On Jul 29, 2006, at 5:01 PM, Lars Rosengreen wrote:
> > This package (64bit version of openmcl) doesn't create any libraries, > > but there is an executable and lisp heap image, both 64bit, and both > > specific to 64bit powerpc processors. Hmm I suppose what I could do > > is depend on the 64bit-cpu virtual package and then also have an > > Architecture: powerpc line in the info file. That seems like it > > should work. I'm not sure about the package name, though. Following > > your lead, I should name the package openmcl-64bit, which seems a > > little too generic in this case. Maybe openmcl-ppc64bit? > > > > Well, I've been trying to set this up so that when we have 64bit > intel processors, one can use the same names, install locations, etc. > for 64bit objects on either processor. Thus, I would recommend using > the Architecture: powerpc flag, but not including ppc in the package > name, since someday a similar facility may become available for intel > as well. > Ok, that makes sense. Thanks again for the help. If anyone wishes to try them out, the info files for sbcl and openmcl-64bit are in my (lrosengreen's) experimental cvs dir. -Lars ------------------------------------------------------------------------- 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
