[kdeconnect-kde/frameworks] kded: Fix dbus activation by using configure_file + install

[Albert Vaca]

I think it can be confusing for the user to have two different ways to
start the service. If the user disables the autostart, he won't expect the
service to still spawn magically because of dbus activation. Why we dont
auto-start some script that keeps kdeconnect alive, instead of spawning
kdeconnect itself? This way we won't need dbus. Or the other way around,
rely only on dbus and not need autostart... Any idea?
On Dec 9, 2014 4:46 PM, "Àlex Fiestas" <afiestas at kde.org> wrote:

> This is the oneliner fix:
>
> QDBusConnection::sessionBus().interface()->startService("org.kde.kdeconnect");
>
> That plus QDBusServiceWatcher and we can have a pretty rock solid system
> watching over kdeconnectd status (replacing our ineffective kded).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20141209/ef2dfaf7/attachment-0001.html>