One of my goals here is to have an automated way to verify that packages are complying with the BuildDependsOnly policy. So I'm trying to find ways of characterizing this which won't get into a lot of exceptions.
Right now (using CVS HEAD or CVS branch_0_20 of fink), the package fails validation if it installs a file into /sw/include or into any subdirectory of /sw/include. 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.) Anybody have examples of this kind of package which we don't want to flag as BuildDependsOnly ? -- Dave P.S. If you are thinking of testing this yourself, the validation only works for .debs built with fink-0.20.3 or later. Older .debs "pass" automatically. ------------------------------------------------------- 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
