David R. Morrison wrote:
Here's an idea for a weaker check: the package would only fail validation if it installs such a header file *and* if it installs any .dylib . (This focusses attention on the shared libraries.)
There would probably be an exception or two to this also. I think we just need a way to flag such exceptions, maybe setting "BuildDependsOnly: false" for that splitoff?
However Martin's example of f77 may be better having Recommends: g77 or Suggests: g77, in part because the user may have another fortran compiler, such as xlf, installed, and in part because g77 is deprecated, a more modern fortran compiler will come with gcc-3.5.
Hope this makes some sense (just got up).
Peter -- Peter O'Gorman - http://www.pogma.com
------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
