strigi analizers install apth

[Jos van den Oever]

2008/5/15 Albert Astals Cid <aacid at kde.org>:
> A Dijous 15 Maig 2008, Alexander Neundorf va escriure:
>> On Thursday 15 May 2008, Albert Astals Cid wrote:
>> > A Dijous 15 Maig 2008, Allen Winter va escriure:
>> > > On Tuesday 13 May 2008 17:26:35 Jos van den Oever wrote:
>> > > > 2008/5/12 Allen Winter <winter at kde.org>:
>> > > > >  Maybe strigi could at some point query kde4-config for KDE's
>> > > > > install directories ?
>> > > >
>> > > > Or we can let strigi look in KDEDIRS. I'd prefer that since it avoid
>> > > > calling kde4-config.
>> > >
>> > > well, startkde already calls kde4-config.
>> > >
>> > > I'm really asking:
>> > > 1) should startkde set $STRIGI_PLUGIN_PATH
>> > > 2) if so, how should it be set? i.e.
>> > >       export STRIGI_PLUGIN_PATH=`kde4-config`/lib/strigi
>> >
>> > That effectively removes from loading any strigi plugin installed system
>> > wide not in `kde4-config`/lib/strigi
>>
>> I guess he meant
>> export STRIGI_PLUGIN_PATH=`kde4-config`/lib/strigi:$STRIGI_PLUGIN_PATH
>
> By default that won't work either, reading strigi code one sees
>
> if (STRIGI_PLUGIN_PATH) readPluginsFrom(STRIGI_PLUGIN_PATH);
> else readPluginsFrom(LIBINSTALLDIR "/strigi");
>
> so most distros won't define STRIGI_PLUGIN_PATH as strigi will already read
> system wide plugins by default, adding STRIGI_PLUGIN_PATH makes that stop
> working.

This should do the trick on distro which have a sane connection
between lib/ and bin/.

f=`which strigidaemon`;
STRIGI_PLUGIN_PATH=`kde4-config`/lib/strigi;${f%bin/strigidaemon}/lib/strigi