+++ This bug was initially created as a clone of Bug #22205 +++ 11:52 < barisione> _run_ functions are evil The reentrant methods in telepathy-glib client code turn out not to be such a good idea. Mission Control hasn't had them for a while, and has a slightly outdated fork of glib-client-gen.py that supports a command-line option to not generate them (and also a command-line option to generate blocking versions, but that's WONTFIX from my point of view, and no longer used anyway). If we add a similar command-line option to telepathy-glib's glib-client-gen.py, we can replace MC's fork with the real one. Also, in the long term (early in the 0.9 series?) we should deprecate _run_ altogether. I've added a command-line option to deprecate these methods, which works per "class". My plan is that when I add Client, ChannelDispatcher etc. bindings, they will lack the _run_ methods altogether; existing classes will keep them, deprecate them in 0.9.0, and delete them when we break ABI.
Here's a branch. It's based on a non-trivial merge of master into next - I don't know whether you want to review that or just say "ship it"?
(In reply to comment #1) > Here's a branch. It's based on a non-trivial merge of master into next (which has now been reviewed, merged)
(In reply to comment #1) > Here's a branch. Yes!
Fixed in next, thanks.
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.