That’s great news, thanks! I think a list of outstanding minor patches (submitted after the large Christmas package from Jordan) which are pending would be: Fixes for a couple of warnings from our statical code analyzer: http://lists.macosforge.org/pipermail/libdispatch-dev/2011-May/000529.html http://lists.macosforge.org/pipermail/libdispatch-dev/2011-May/000530.html And a couple of Linux specific ones from Mark Heily: http://lists.macosforge.org/pipermail/libdispatch-dev/2011-June/000532.html http://lists.macosforge.org/pipermail/libdispatch-dev/2011-June/000559.html Sounds like a very good idea to start using the trac system more consistently going forward… Cheers, Joakim On 16 aug 2011, at 23:32, Daniel A. Steffen wrote:
The Lion libdispatch sources are now available: http://www.opensource.apple.com/release/mac-os-x-107/ http://www.opensource.apple.com/tarballs/libdispatch/libdispatch-187.5.tar.g...
The configure/make buildsystem has been updated to produce a working libdispatch.dylib on Lion that can be used/installed in place of the stock version, see INSTALL for details.
Next steps are to decide how to integrate the new sources into the macosforge repository; as you will discover, there has been significant refactoring/reorganization, making this not completely trivial.
As a first step I was planning to import the Lion source drop on a branch, and then start reorganizing trunk similarly to make trunk changes that are missing from the branch more apparent.
Before I get started on that we should make sure that all pending non-controversial patches are integrated onto trunk, does anybody have a list of what is still outstanding? (I guess this is where more consequent use of the trac ticket system on http://libdispatch.macosforge.org/trac/report would be paying off..)
Daniel _______________________________________________ libdispatch-dev mailing list libdispatch-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/libdispatch-dev