#27563: libnotify update to 0.5.2 -----------------------------------------+---------------------------------- Reporter: markus.doits@… | Owner: ryandesign@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: haspatch | Port: libnotify -----------------------------------------+---------------------------------- Comment(by ryandesign@…): Ah, +quartz; I haven't used that. From the NEWS file in the libnotify 0.6.0 distfile I see: {{{ NEW in 0.6.0: ============== The 0.5.1 release included changes that should not have been made on a stable branch. It should have been a 0.6 series release. So here it is. - Fixed #623096 Fix notify_get_server_info results NEW in 0.5.1: ============== - Remove explicit GTK+ 2.x linking, so that libnotify can link against both GTK+ 2.x or GTK+ 3.x }}} What I learn from this is: * 0.5.x is a stable branch after all * 0.5.x can use gtk2 or gtk3 (You demonstrated 0.5.2 could use gtk2) * there is no entry for 0.5.2 From the NEWS file in the libnotify 0.5.2 distfile I see: {{{ NEW in 0.5.2: ============== Note that the 0.5.1 release was released from the 0.6 branch in error. Sorry about that. - Fixed #623096, Use correct variable in NULL check - Added a macro NOTIFY_CHECK_VERSION }}} So I guess that means we can update to 0.5.2 after all. I incorrectly guessed they used the odd-number-is-unstable rule, based on experience with other GNOME software (like gtk2, glib2, and pango), and I could not find a libnotify web site or release announcements from which to learn their actual policies. -- Ticket URL: <https://trac.macports.org/ticket/27563#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS