Re: ksycoca and kbuildsycoca, the next step

2015-09-07 Thread David Faure
On Sunday 06 September 2015 18:15:47 Matthew Dawson wrote: > On September 7, 2015 12:03:59 AM you wrote: > > On Sunday 06 September 2015 17:59:13 Matthew Dawson wrote: > > > On September 6, 2015 01:52:37 PM David Faure wrote: > > > > As a followup to recent discussions, I'm now looking into moving

Re: ksycoca and kbuildsycoca, the next step

2015-09-06 Thread Jeremy Whiting
That sounds like a good solution to all the problems you presented initially indeed. Nice work. On Sun, Sep 6, 2015 at 3:43 PM, David Faure wrote: > On Sunday 06 September 2015 13:52:37 David Faure wrote: >> >> Any idea on how to avoid cache-rebuild ping pong? >> >> I can only

Re: ksycoca and kbuildsycoca, the next step

2015-09-06 Thread Matthew Dawson
On September 6, 2015 01:52:37 PM David Faure wrote: > As a followup to recent discussions, I'm now looking into moving the > recreating kbuildsycoca directly into the kservice library. > > The rebuild now happens on demand when using any KService API and one the > dirs with desktop files is more

Re: ksycoca and kbuildsycoca, the next step

2015-09-06 Thread Matthew Dawson
On September 7, 2015 12:03:59 AM you wrote: > On Sunday 06 September 2015 17:59:13 Matthew Dawson wrote: > > On September 6, 2015 01:52:37 PM David Faure wrote: > > > As a followup to recent discussions, I'm now looking into moving the > > > recreating kbuildsycoca directly into the kservice

Re: ksycoca and kbuildsycoca, the next step

2015-09-06 Thread David Faure
On Sunday 06 September 2015 13:52:37 David Faure wrote: > > Any idea on how to avoid cache-rebuild ping pong? > > I can only think of one cache per (lang, dirs) combination somehow, but that > seems tricky > (a config file to point to some randomly generated filename for each > combination?).

Re: ksycoca and kbuildsycoca, the next step

2015-09-06 Thread David Faure
On Sunday 06 September 2015 17:59:13 Matthew Dawson wrote: > On September 6, 2015 01:52:37 PM David Faure wrote: > > As a followup to recent discussions, I'm now looking into moving the > > recreating kbuildsycoca directly into the kservice library. > > > > The rebuild now happens on demand when

ksycoca and kbuildsycoca, the next step

2015-09-06 Thread David Faure
As a followup to recent discussions, I'm now looking into moving the recreating kbuildsycoca directly into the kservice library. The rebuild now happens on demand when using any KService API and one the dirs with desktop files is more recent than the sycoca cache (that part is already in), so the