[Bug 56635] make NM/ConnMan integration into plugins or use GNetworkMonitor?

[bugzilla-daemon at freedesktop.org]

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

Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
            Summary|Make NetworkManager         |make NM/ConnMan integration
                   |dependency optional         |into plugins or use
                   |                            |GNetworkMonitor?

--- Comment #1 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
Enabling the NetworkManager integration adds a hard dependency on a couple of
(relatively small) libraries supplied by NetworkManager: if Arch's
infrastructure turns that into a dependency on the NM daemon itself, I'd
consider that to be a problem with that infrastructure.

For instance, in Debian[1], on Linux architectures the
telepathy-mission-control-5 binary package has a hard dependency on the
libnm-glib4 binary package, but no dependency on the network-manager binary
package. The libnm-glib4 and network-manager binary packages are both built by
the network-manager source package (similar to "subpackages" in RPM jargon).

[1] <http://packages.debian.org/experimental/telepathy-mission-control-5>

Having said that, it would be nice if the NM and ConnMan integration could be
done either as a plugin (with a sensible, stable API via
libmissioncontrol-plugins, that doesn't expose MC internals like the old
McdTransport API did), or by using GNetworkMonitor. Severity -> enhancement for
that.

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