I was thinking during doing the debug sender stuff how Telepathy is restricting itself with respect to log levels. Pretty much everywhere just uses DEBUG. Although I'm not volunteering to go through our CMs and Empathy making sure DEBUGs become more appropriate levels where appropriate, it'd be nice if it was easy to do so with new/modified code. So I wrote the linked branch against master. Check it out.
This makes sense, although perhaps gabble_debug() should also be renamed to gabble_log(). Could you do something similar in telepathy-glib's debug-internal.h? We could benefit from some sort of policy for what level to use where - extremes are Mission Control (which emits a g_warning on some relatively normal conditions, like a channel request failing) and e.g. Gabble (which criticals when API is used wrong, but basically never warns). I think the correct policy is somewhere in between. (Note that warnings can be made fatal in the environment, which we do in most non-MC regression tests - it'd probably be better for MC to do a MESSAGE or INFO on failed channel requests, for this reason.)
(In reply to comment #1) > This makes sense, although perhaps gabble_debug() should also be renamed to > gabble_log(). Okay, I've done this. > Could you do something similar in telepathy-glib's debug-internal.h? Sure. I also added another patch to fix the build (when these new macros are actually used) with --disable-debug. Bad me. So, the two additional commits look okay?
(In reply to comment #2) > So, the two additional commits look okay? They do. Ship it!
Merged, will be in next 0.9 release.
This has the same problems as Bug #27899.
... and indeed, so does Salut. I don't propose to file a separate bug for Salut.
I've reverted the Salut patch til we can replace it with something based on this one. Sorry, I should have spotted this at review.
smcv's patch to fix this looks fine, so I have merged it.
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.