Dear Fink developers and users, I've just published the results of a buildworld run on a 10.9 system. The buildworld tries to build every package in the Fink tree from scratch on a clean environment and so will find packaging problems that may be hidden on a production system.
The general report broken down by results category is here: http://www.snaggledworks.com/fink/buildworld/2014-07-24/out/report.html The listing by maintainer is here: http://www.snaggledworks.com/fink/buildworld/2014-07-24/out/maintindex.html The algorithm to categorize failures is very basic and does have some false positives. In short, it searches every package build log for a match to the list of known errors. If one of the error tokens is found in the buildlog, that package will be reported as a failure, even if the package actually built successfully as expected. The buildworld also has a simple search function for the contents of every generated .deb file if you need to find what package provides a specific file (useful for tracking down dependencies). I have also saved the build directories for failed packages. If the build log does not have enough information to analyze a failure, I can provide the contents (such as config.log) of the specific build upon request. Note: a buildworld is not a continuous process (unlike a bindist). It is a (mostly) static picture of Fink's package database when it started. If a package was updated in CVS after July 24, 2014, there is a very good chance that it did _not_ get updated in the local buildworld machine. If Follow up with questions and comments to the fink-devel list. Hanspeter ------------------------------------------------------------------------------ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
