Possible clash in ~/.kdevduchain

Aleix Pol aleixpol at kde.org
Mon Aug 2 16:37:00 UTC 2010


On Mon, Aug 2, 2010 at 5:21 PM, Milian Wolff <mail at milianw.de> wrote:

> On Monday, 2. August 2010 17:14:00 Aleix Pol wrote:
> > On Mon, Aug 2, 2010 at 3:48 PM, Milian Wolff <mail at milianw.de> wrote:
> > > Hello,
> > >
> > > I just noticed that in theory the stored duchain caches in
> ~/.kdevduchain
> > > may
> > > clash when we have more and more applications using KDevplatform.
> > >
> > > The reason is:
> > >
> > > - sessions are stored in  ~/.kde/share/apps/$APP/sessions/$SESSION
> > > - all applications store their chains in ~/.kdevduchain/$SESSION though
> > >
> > > so if two apps have by chance the same session hash, it will lead to a
> > > clash
> > > in the duchain cache.
> > >
> > > How should we solve this? Afaik now that the chain loading is delayed,
> we
> > > can
> > > access KAboutData or what it was to get the name of the application.
> That
> > > would mean we can do something like:
> > >
> > > ~/.kdevduchain/$app/$SESSION
> > >
> > > otoh we could directly move this stuff to
> > > ~/.kde/share/apps/$APP/$SESSION/duchain
> > >
> > > Maybe the latter is even better as it's clear that only app data is
> > > stored there... What do you think?
> >
> > We can lock sessions for all consumers, no? (if a session is already
> being
> > used by kdevelop then it shouldn't be used from quanta)
>
> Why should sessions in quanta be the same as in KDevelop? I don't like that
> idea at all.
>
To be able to share data.
If there's none ever going to be shared there's no point on doing that, but
given that technically it's trivial you can consider that. Otherwise
.kde4/share/apps is just fine


>
> > > Moving it to .kde/share/apps would make it clearly harder to clean the
> > > chain
> > > though. I'd hence also add some more cli-arguments to kdevelop (and
> > > quanta) to
> > > clean a chain.
> > >
> > > Something like:
> > >
> > > kdevelop --wipe-duchain --session $name
> >
> > we could have a new command like kdev-cleanduchain $name too.
>
> Why? I hate to have multiple tools to stuff on the same base. You can have
> a
> alias for kdev-cleanduchain, not the other way around.
>

Just a matter of taste. We can discuss that on the future, though.


> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100802/24848b0b/attachment.html>


More information about the KDevelop-devel mailing list