Hi,

David (Faure) mentioned he's been working to port the kcookiejar away from 
kded5 (maybe that has advantages on *n*x too?). Idem for the automatic sycoca 
regeneration, IIRC.

I've been running kded4 and now kded5 as part of a "fullest possible" build & 
install principle under MacPorts on OS X. That's more or less a prerequisite if 
you want cookie support but also support for certificate management in KDE(4) 
applications. I also see even less reason to run that daemon than to run a DBus 
daemon on "other platforms". It's a KDE application that provides background 
services to other KDE apps, and any platform specificity resides in the 
services it runs, not the daemon itself. It probably wouldn't even be very hard 
to think of other-platform-specific services that it might run, a bit like how 
the Baloo framework might provide an interface to Spotlight on OS X (or KWallet 
to the keychain).

Anyway, taking stock of what else I have running I saw the "Network Status" 
service as probably the only other potentially relevant service.
Is this what allows akonadi/KDE PIM to detect when network goes off and on 
line? Because that's a feature that does seem to work in KMail4 c.s. on OS X, 
and it's something I definitely wouldn't want to lose if and when I move to KF5 
PIM.

R.


_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

Reply via email to