Benjamin Place wrote:
--- Martin Costabel <[EMAIL PROTECTED]> wrote:
We already have examples of packages that depend on
external stuff like specific commercial fortran
compilers or parts of the developer tools that are
not installed by default, and which manage their
dependencies on these external components "by hand",
not via virtual packages.
Could you point me to a couple to use as examples?
In sci, there are netcdf-absoft and fftw-absoft that need the absoft
fortran compiler installed. They manage their dependency on this via the
system-fortran package (not a virtual package, just a dummy). There are
other such system-* placeholder packages, like system-viha (and of
course the classics system-tetex and system-ghostscript).
I have a package "melina-ibm" in my experimental directory that uses the
IBM fortran compiler. It is not an ideal example, because it does no
checking.
Then there is net/net-snmp.info which uses a SetCPPFLAGS value of
-I/Developer/SDKs/MacOSX10.3.0.sdk/usr/include. This is actually a bad
example, because it doesn't do any checking nor much explaining, it just
doesn't build if you don't have this SDK installed. It also has kept
this stuff on Tiger, although there is no such thing as a
MacOSX10.3.0.sdk there and the trick is not needed. Actually, there are
now virtual packages representing the various /Developer/SDKs, but I
don't see any package that uses them.
--
Martin
-------------------------------------------------------
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
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
