telepathy-glib 0.7.14 needs glib2 2.16 I get this error: contacts-mixin.c:107: error: 'GHashTableIter' undeclared (first use in this function) configure does not check for glib 2.16 that introducted 'GHashTableIter'. It should.
True. I'm not sure whether the correct fix here is to require GLib 2.16, or construct some sort of TpGHashTableIter (implemented as: iterate the hash table, stuff the keys into a GSList, iterate the GSList, an explicit call to tp_g_hash_table_iter_free will be required).
If the iteration is on tight code paths, I'd vote for 2.16.
Some useful information about a bunch of distros, to see whether we care about not supporting 2.14: 2.16 is in Ubuntu >= hardy <http://packages.ubuntu.com/search?suite=all&searchon=names&keywords=libglib2.0-0>. hardy is LTS, so I think it's the oldest release we care about. It will be in Debian lenny <http://packages.debian.org/search?keywords=libglib2.0-0>, which I think is the oldest we care about. Only 2.12 is in Maemo diablo <http://tablets-dev.nokia.com/4.1/4.1_vs_4.0.1_content_comparison.html>, but putting a telepathy-glib on a tablet is a backport of a system package in any case, so backporting GLib too isn't necessarily so bad... 2.16 is in Fedora 9 but not in Fedora 8 <https://admin.fedoraproject.org/updates/glib2>. 2.16 is in OpenSUSE 11 but not 10.3 <http://packages.opensuse-community.org/index.jsp?distro=openSUSE_110&searchTerm=glib2>.
> 2.16 is in OpenSUSE 11 but not 10.3 > <http://packages.opensuse-community.org/index.jsp?distro=openSUSE_110&searchTerm=glib2>. > It is the build on 10.3 that blew here.
Commit fcbb77 <http://git.collabora.co.uk/?p=telepathy-glib.git;a=commitdiff;h=fcbb772569ef26d8c27b2602c26e5d9121f75355> officially bumps the requirement to 2.16. This will be in telepathy-glib 0.7.15, unless someone can explain why we should continue to support older versions of GLib (e.g. Fedora 8, Debian etch or OpenSuse 10.3 without a GLib backport).
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.