Am Dienstag, 14. April 2015, 13:17:56 schrieb Sandro Knauß: > Hi, > > > I use default /usr/local location and do as little customization of > > the > > build process as possible. Then I tell my KDE sessions to use > > /usr/local > > stuff as well like this: > This does not touch all relevant env variables (see attached script). It > is configured to have > ~/kde/src/<name>/kdepim - source > ~/kde/build/<name>/kdepim - build > ~/kde/inst/<name> - install dir I just have ~/KDE/Dev, git clone what I need, do mkdir build, cmake .., make -j4, sudo make install on what I need. I know all manual, but > after running the script you have to do something like: > > setKDEEnv master > > Okay it additionally also makes sure that you have different home dirs > etc. > > In your case the folling env variables should be enough to set: > > XDG_DATA_DIRS - needed for akonadi resources > LD_LIBRARY_PATH - to find libs > KDEDIRS > KDEDIR > KDEHOME > PATH > QT_PLUGIN_PATH I have seen such scripts, but they do a lot, a lot more than I usually want, and I think the version from /usr/local is used with my minimal script already. I don´t start with a full blown vim configuration either. But just change what I need. And as to far as I have seen, this minimal approach just works for me: martin@merkaba:~> akonadictl status Akonadi Control: running Akonadi Server: running search paths: ("/usr/local/lib/kde4", "/home/martin/.kde/lib/kde4/plugins/", "/usr/local/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/local/lib/plugins/", "/usr/lib/x86_64- linux-gnu/qt4/plugins", "/usr/local/bin", "/usr/local/lib/kde4/plugins", "/usr/lib/kde4/plugins", "/usr/local/lib/plugins", "/home/martin/.kde/lib/kde4/", "/usr/local/lib/kde4/", "/usr/lib/kde4/") […] martin@merkaba:~> ps -eo cmd | grep akonadi | cut -c1-60 /usr/bin/akonaditray -session 10cec7d36b00013604921290000002 /usr/local/bin/akonadi_control akonadiserver /usr/sbin/mysqld --defaults-file=/home/martin/.local/share/a /usr/local/bin/akonadi_agent_launcher akonadi_akonotes_resou /usr/local/bin/akonadi_agent_launcher akonadi_akonotes_resou /usr/local/bin/akonadi_archivemail_agent --identifier akonad /usr/bin/akonadi_baloo_indexer --identifier akonadi_baloo_in /usr/local/bin/akonadi_birthdays_resource --identifier akona /usr/local/bin/akonadi_agent_launcher akonadi_contacts_resou /usr/local/bin/akonadi_followupreminder_agent --identifier a /usr/local/bin/akonadi_icaldir_resource --identifier akonadi /usr/local/bin/akonadi_imap_resource --identifier akonadi_im /usr/local/bin/akonadi_agent_launcher akonadi_maildir_resour /usr/local/bin/akonadi_maildispatcher_agent --identifier ako /usr/local/bin/akonadi_mailfilter_agent --identifier akonadi /usr/local/bin/akonadi_migration_agent --identifier akonadi_ /usr/local/bin/akonadi_newmailnotifier_agent --identifier ak /usr/local/bin/akonadi_notes_agent --identifier akonadi_note /usr/local/bin/akonadi_pop3_resource --identifier akonadi_po /usr/local/bin/akonadi_pop3_resource --identifier akonadi_po /usr/local/bin/akonadi_pop3_resource --identifier akonadi_po /usr/local/bin/akonadi_pop3_resource --identifier akonadi_po /usr/local/bin/akonadi_pop3_resource --identifier akonadi_po /usr/local/bin/akonadi_pop3_resource --identifier akonadi_po /usr/local/bin/akonadi_sendlater_agent --identifier akonadi_ All local. Except Baloo, which I do not build at the moment, but use the packaged one. And well akonaditray, but it comes from kdepim-runtime, hmmm, okay, don´t know why it doesn´t pick it up, ok, thats one omission. merkaba:~> which -a akonaditray /usr/local/bin/akonaditray /usr/bin/akonaditray May be do it it being started from Plasma and Plasma needing another part? I don´t care that much for it tough, cause I don´t need it newer than whats packaged. martin@merkaba:~> ldd /usr/local/bin/kmail | tr -d "\t" | cut -c 1-70 | head -20 linux-vdso.so.1 (0x00007ffe741fc000) libkdeui.so.5 => /usr/lib/libkdeui.so.5 (0x00007f2092143000) libkdecore.so.5 => /usr/lib/libkdecore.so.5 (0x00007f2091c54000) libkontactinterface.so.4 => /usr/local/lib/libkontactinterface.so.4 (0 libkmailprivate.so.4 => /usr/local/lib/libkmailprivate.so.4 (0x00007f2 libkdepim.so.4 => /usr/local/lib/libkdepim.so.4 (0x00007f20912cd000) libQtScript.so.4 => /usr/lib/x86_64-linux-gnu/libQtScript.so.4 (0x0000 libkldap.so.4 => /usr/local/lib/libkldap.so.4 (0x00007f2090bdd000) libkpimidentities.so.4 => /usr/local/lib/libkpimidentities.so.4 (0x000 libkpimtextedit.so.4 => /usr/local/lib/libkpimtextedit.so.4 (0x00007f2 libakonadi-contact.so.4 => /usr/local/lib/libakonadi-contact.so.4 (0x0 libkpimutils.so.4 => /usr/local/lib/libkpimutils.so.4 (0x00007f2090272 libkcalcore.so.4 => /usr/local/lib/libkcalcore.so.4 (0x00007f208ffa200 libphonon.so.4 => /usr/lib/x86_64-linux-gnu/libphonon.so.4 (0x00007f20 libkabc.so.4 => /usr/local/lib/libkabc.so.4 (0x00007f208fa74000) libkresources.so.4 => /usr/local/lib/libkresources.so.4 (0x00007f208f8 libakonadi-kde.so.4 => /usr/local/lib/libakonadi-kde.so.4 (0x00007f208 libkmime.so.4 => /usr/local/lib/libkmime.so.4 (0x00007f208f0e2000) libkio.so.5 => /usr/lib/libkio.so.5 (0x00007f208ec04000) libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x00 What necessary is local as well merkaba:/etc/ld.so.conf.d> cat libc.conf # libc default configuration /usr/local/lib And KMail tells me it is 4.14.7. I see nothing missing. And I want it to use my production config. Cause I use this for production. Its near enough to the versions packaged in Debian. Heck, this even works with kmail Debian package still installed. Cause $PATH prefers /usr/local. So for me its all good. For building KF5 and Plasma 5, I think I need more, but I want to wait till packages are installable and then only build from source what I need and then tell it to reuse my production config as well. This way I can use from distro, what I want, and I can use self-compiled what I want. Of course, it can give conflicts, I had once some files in /usr/local that crashed some app, but well, I am willing to live with the risk. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Attachment:
signature.asc
Description: This is a digitally signed message part.