Empathy has a GSettings key which allows advanced users to instruct it to assume it's always online, even if NM claims otherwise. This is particularly useful for Telepathy hackers on trains and planes, using a local XMPP server for testing. ;) MC currently has no way to do this. Alex Larsson suggested a way (endorsed by Ryan Lortie) to give MC a GSettings key which is kept in sync with the Empathy one. The approach is to define a schema whose identifier is im.telepathy.MissionControl.StolenFromEmpathy but whose path is /org/gnome/empathy/ which has a single key, 'use-conn'. This would mean a separate setting would be visible in (say) gsettings list-recursively, but under the bonnet they would use the same value stored in dconf. So this gives us a migration path that doesn't make MC depend on Empathy or require syncing versions of the two up too closely.
Well, I have a branch here, but it doesn't work, and I can't figure out why not. It always believes the key to be true, and doesn't react to changes. (But the gsettings command-line tool reads the value properly…)
Oh actually it does work. Ignore me. (Well, don't ignore me! Review my branch!)
+export GSETTINGS_SCHEMA_DIR=@abs_top_builddir@/data More portable as: GSETTINGS_SCHEMA_DIR=@abs_top_builddir@/data export GSETTINGS_SCHEMA_DIR Other than that, looks good.
Fixed the trivia (and another non-POSIX export) and merged; thanks! <http://cgit.freedesktop.org/telepathy/telepathy-mission-control/commit/?id=b89a27403d632725504c21c6079b936f9c1c6c9c>
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.