Move of kglobalacceld from plasma-workspace to kglobalaccel framework
faure at kde.org
Sun Jan 4 13:11:06 UTC 2015
On Friday 19 December 2014 17:46:07 šumski wrote:
> On Thursday 18 of December 2014 20:15:52 Martin Klapetek wrote:
> > On Wed, Dec 17, 2014 at 9:11 PM, šumski <hrvoje.senjan at gmail.com> wrote:
> > > Hi,
> > > i've checked your clone, and what new requirements will that bring, and
> > > if the
> > > CMakeLists there are accurate, that will create a problem.
> > > We will have a dependency circle between kglobalaccel, kinit, kio and
> > > kxmlgui.
> > Bah, I think you're correct. Basically the only link in this dep circle is
> > KBookmarks
> > using KActionCollection from xmlgui if I'm reading it correctly. If this
> > is
> > removed,
> > then I think the circle would be gone.
> KIO requires both KBookmarks and KXMLGui, so i am not sure how changing
> something in KBookmarks only would change the cycle...
> One possible solution, but no idea would that be OK, is to make the
> kglobalaccel 'regular' executable, instead of a kdeinit one...
That's definitely an option, it only makes a difference in terms of startup
time, for one daemon we can do without the kdeinit optimization, if it solves
a circular dependency.
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
More information about the Kde-frameworks-devel