kdeinit (was: Summary from Buildsystem BoF at Desktop Summit)
neundorf at kde.org
Mon Aug 22 21:07:16 BST 2011
On Saturday 20 August 2011, Thiago Macieira wrote:
> On Saturday, 20 de August de 2011 10:02:31 Oswald Buddenhagen wrote:
> > On Tue, Aug 16, 2011 at 08:58:02PM +0200, Thiago Macieira wrote:
> > > frameworks (qt-based), applications and workspace, that sounds pretty
> > > much what the KDE Platform is. What are you excluding in your
> > > definition?
> > >
> > > kded, klauncher, kdeinit, kglobalaccel, kwallet?
> > yes, among other things.
> > kded's module activation is redundant with systemd.
> But not at all the same impact. Starting an application and negotiating its
> connection to D-Bus is hardly comparable to loading a plugin in a daemon
> that is already connected.
> > as it happens, lennart also made a mini-daemon dealing with host name
> > changes, which is another thing kded does.
> > klauncher is conceptually redundant with systemd as well. the backend it
> > uses is kdeinit, which *should* be in systemd - it's not like it would
> > not benefit gnome as well (otherwise there would be no maemo booster) -
> > we just need some fresh numbers to justify the hack, and some arguments
> > why the hack isn't *that* bad after all.
> That I agree: klauncher is systemd for KDE only, so we should see about
> getting the same benefits from systemd instead.
> There are two drawbacks with that, though:
> 1) systemd will not likely ever run on non-Linux systems, not even the
> BSDs. Lennart simply isn't interested on ensuring compatibility and might
> even reject patches which introduce differences to Linux-specific
Wouldn't that also make us require Linux systems which actually run systemd ?
I guess Slackware would be out then.
More information about the kde-core-devel