"glademm an extension to glade and glade-2 (Gtk GUI Builder) to create C++ sources for gtk-- and gtkmm2 (any combination) or skeletons for libglade(mm) based programs." 2.0.0.1 is in portage, 2.5.0 is not. http://home.wtal.de/petig/Gtk/glademm-2.5.0.tar.gz
versioning suggests it might be unstable
According to http://home.wtal.de/petig/Gtk/index.html it does not appears to be unstable (it does not say it is stable either). He also wrote: "Use cvs to get the latest fixes, I only release an official tarball here once I feel that the old release is outdated too much." Considering this, and the numbering diference in portage, we can assume that 2.0.0.1 is "too much outdated".
so i can take it you are a user of this package. What improvements does it bring that this needs to be prioritized ?
The new version compiles cleanly (at least on my machine) by just bumping the ebuild. Here's the changelog since 2.0.0.1: Version 2.5.0 - support CAN_DEFAULT/HAS_DEFAULT (Howdy Pierce) - initial gtk+ 2.4 work (test) - fixed nasty autoconf bug (missing closing bracket on autoconf2.50+) - hopefully fixed gettext/autotool bugs [working with gtk2.4, gnome1, gtk1] - recognize and look for gtkmm 2.4, default to compatibility code Version 2.0.0.2 - use AC_CONFIG_HEADERS on autoconf2.50+ - some error checking for embedded images - try to determine automake/autoconf postfix for newer autoconf setups - default to all widgets visible if all are private (beginners' #1 error) and tell the users about this in the headers (which they tend to read before any documentation ...) - do not generate acconfig.h for autoconf2.50+ - gnome1 fixes for button (stock_pixmap)
i wasn't asking for the changelog.. you dodged the question...
Yeah, I did :) The main improvement is support for the gtk 2.4 libraries. I didn't try the 2.0.0.1 with it since the docs said it didn't support, so I installed 2.5. I had no trouble with it yet.
but that is in testing according to the changelog & that sort of gives me the impression it is a devel release.
*** Bug 72412 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 74415 ***