cyclic dependency kinit - kservice

David Faure faure at kde.org
Sun Oct 27 09:34:33 UTC 2013


On Sunday 27 October 2013 06:26:21 Nicolás Alvarez wrote:
> El domingo, 27 de octubre de 2013, David Faure escribió:
> > On Friday 25 October 2013 18:27:02 Kevin Ottens wrote:
> > > On Friday 25 October 2013 12:21:28 David Narvaez wrote:
> > > > On Fri, Oct 25, 2013 at 11:37 AM, Kevin Ottens
> > > > <ervin at kde.org<javascript:;>>> 
> > wrote:
> > > > > Not that I know of, Alex never replied to that I think...
> > > > 
> > > > What would be a proper fix for this? Separating kbuildsycoca and
> > > > putting it on top of kinit?
> > > 
> > > I'd lean more toward having kbuildsycoca not be a kdeinit module. David
> > > (Faure) knows more that area than me though...
> > 
> > Right, we can do that. kbuildsycoca is a background process, the user will
> > never notice if it takes a little bit longer to start.
> 
> Does kdeinit have a noticeable startup-speed advantage on modern systems?
> The benchmark in the kdeinit README looks quite old...

I'm told that the answer is yes - IIRC because relocations take time and are 
avoided that way. Meego and family use(d) a very similar trick, showing that 
this isn't only a 1998 issue.

But I would be very happy if someone could take the time to measure it, so 
that we can be sure!

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5



More information about the Kde-frameworks-devel mailing list