On Jan 10, 2006, at 10:05 PM, Lars Rosengreen wrote:

On 1/10/06, David R. Morrison <[EMAIL PROTECTED]> wrote:

On Jan 6, 2006, at 1:44 PM, Asko Kauppi wrote:


I have a package for Fink that is completely CPU ignorant; how
should I mark it such in the .info file?

That's the default behavior; no need to mark anything.

If it has been discussed on the list and I missed it, I appologize,
but how should I handle cases where it should not be the default
behavior, some examples being the various common lisp packages I
maintain?

No, it hasn't been discussed before, you didn't miss anything!

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).

The Architecture field is now (briefly) documented in the packaging manual, and there is also some discussion on the developer wiki.

Of course, the big problem at the moment is that unless you know a developer with an Intel development machine or a friend with an early- shipping iMac or MacBook Pro, there is no way to test whether your package works on Intel or not!

  -- Dave




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to