[Kmymoney] Re: [Kmymoney-devel] Re: Install into /home - Plugins not found

[aga]

Hi Jack

On Tue, 01 Feb 2011 13:21:08 -0500
Jack <ostroffjh at users.sourceforge.net> wrote:

> Hello,
> 
> I haven't played with doing a local install recently, but I did spend
> a lot of time at it, including discussions on the KDE forums.  I
> don't know if I can help Allan, since I never had to worry about
> plugins, but some of what I discovered might help.
> 
> I assume you are not having a problem with getting the installed
> files to go to the right place, but with that copy finding the
> plugins at runtime.  Rereading your message, I see this is not quite
> the case, but are the plugins that are getting installed to the
> "wrong" place being compiled alone or as part of building KMM?

 The basic problem is not knowing what is the "wrong" place, or the
 right place.  Until recently, I've had parallel installations in /usr
 and /home.  I'm restructuring the UI for the CSV plugin and found that
 the 'old' UI was still being loaded from /usr.  Initially, I just
 renamed that plugin and all seemed well - that is, until I uninstalled
 the /usr version and found that my /home version was not finding the
 CSV plugin.  In fact, although I did not notice it initially, now, on
 loading KMM, I get a message that -
"kmymoney(27422)/kdecore (trader) KServiceTypeTrader::defaultOffers:
KServiceTypeTrader: serviceType  "KMyMoneyPlugin"  not found", so it's
not just my tinkering at fault, but more basic, ie. all plugins are
missing, or rather not discovered.  

The problem seems to be the location used for installation of the
plugin rc files.  Normally, they all go in /usr/share/kde4/apps/, but
when installing locally, they go in ~/share/apps/ (no kde directory).
The plugin desktop and .so files are picked up correctly.

I've tried copying to several possible alternative locations but no
luck.  I'll continue looking for where the file is supposed to be.

>  In
> any case, I think the problem may have to do with how KDE looks for
> things at runtime.  Some of what an application looks for (more
> accurately, where it looks for things) may be set at compile and
> install time, but others are based on settings established when KDE
> starts up.  Some of these things can be changed by altering
> environment variables or config files and rerunning kbiuldsycoca4,
> but some cannot.
> 
> The example that bothers me the most is that if I install a locally  
> compiled version of KMM in my own area, I can run it and get it to
> pick up most of the various bits and pieces, but not the new
> handbook.  The mechanism for KDE finding a handbook gets set when KDE
> starts, and so I could add my local area to the KDEDIRS path before
> starting KDE, but then if I ran the distro installed version, it
> would pick up my local handbook, and possibly some other pieces.
> 
> I'm still not certain this is related to the problem you are having
> - but it sounds similar.
> 
> Jack
> 
It certainly sounds similar.

Allan