[Bug 70458] connectivity monitor depends on now-removed upower API

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Oct 15 13:05:31 CEST 2013


https://bugs.freedesktop.org/show_bug.cgi?id=70458

--- Comment #5 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
(In reply to comment #4)
> fwiw, UPower master isn't targetted for GNOME 3.10, but for GNOME 3.12.

Mission Control 5.16.x has both UPower and logind suspend-detection, and is
recommended for use with GNOME 3.10. 5.17.x (where I suggest this change)
targets GNOME 3.12.

However, we do try to avoid being tied to particular GNOME releases: Telepathy
is a cross-desktop project (also used in KDE, for a start), and we aim for it
to be safe for distros to upgrade Telepathy while using the previous GNOME
release.

If the UPower release that deletes this API will have a known version number,
we could change the pkg-config check from [upower-glib] to [upower-glib < 0.10]
or [upower-glib < 0.9.23] or something, resulting in our UPower support being
disabled for newer upower-glib?

(That would be better for the 5.16.x branch, anyway - I'm not going to remove
features from a stable-branch, but I wouldn't mind tightening the condition
under which that feature is available.)

I'd rather not get into AC_CHECK_FUNC([up_client_suspend_sync]) or similar,
since it doesn't combine well with pkg-config.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the telepathy-bugs mailing list