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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Apr 30 18:42:14 CEST 2013


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |guillaume.desmottes at collabo
                   |                            |ra.co.uk,
                   |                            |josh at linux.intel.com,
                   |                            |xclaesse at gmail.com

--- Comment #4 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
I have a patch-set that works for the regression tests (but possibly not in
real life). I'm going to test it in a few real configurations (NM with netlink
GNetworkMonitor, ConnMan with netlink GNetworkMonitor, ConnMan with
<https://github.com/jukkar/connman-network-monitor>), but I think it's ready
for review while I do that.

(In reply to comment #2)
> Archlinux likes to keep things
> simple, and splitting up packages is not the done thing.

I still think this is a packaging bug - distributions that separate library and
daemon packages don't do it for fun, they do have valid reasons, and this is
one of them. However, with this patch-set, building with
"--with-connectivity=no" will avoid the dependency on network-manager
libraries, and the only feature that'll be lost on NM systems is that MC won't
automatically disconnect everything (in the hope that the network is still
briefly usable) when NM reports CONNECTING, DISCONNECTING or ASLEEP status.

If Telepathy reviewers' opinion is that special handling of the CONNECTING,
DISCONNECTING and ASLEEP statuses is not worth bothering with at all, then we
can cut out the HAVE_NM code path and just use GNetworkMonitor everywhere. In
the longer term, Bug #41148 is probably a better approach to that anyway.

-- 
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