Bug 357438

Summary: Private libs should go to /usr/lib/$arch/kbibtex
Product: [Applications] KBibTeX Reporter: roucaries <roucaries.bastien+bugs>
Component: Compiling/packagingAssignee: Thomas Fischer <fischer>
Status: RESOLVED NOT A BUG    
Severity: minor Keywords: triaged
Priority: NOR    
Version First Reported In: git (master)   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description roucaries 2016-01-02 17:18:27 UTC
Hi,

libkbibtexconfig0.8 libkbibtexdata0.8 libkbibtexgui0.8 libkbibtexio0.8 libkbibtexnetworking0.8 libkbibtexproc0.8 are private libs only intented to use by kbibtex.

could you put these libs to  /usr/lib/$arch/kbibtex and put -L cflags ?

Bastien
Comment 1 roucaries 2016-01-11 22:49:38 UTC
Alternatvly you could use static linking of this convenience lib
Comment 2 Thomas Fischer 2016-01-12 12:21:11 UTC
Back in the old days of KDE4 and Nepomuk, someone wrote an bibliography indexer that made use of those libraries. I guess that with KF5 and Baloo, this is history.
Can you tell me how I have to modify the CMakeLists.txt files to achieve your request? An example for one library should be sufficient. Please avoid any hard-coded paths, as those tend to break at some point.
Comment 3 Thomas Fischer 2016-12-25 22:01:19 UTC
Revisiting this bug: I tried to find some positive examples where KF5 programs install their private libraries some place else than /usr/lib or /usr/lib64.
So far, no program does it differently than KBibTeX.
For example, Konsole installs libkonsoleprivate.so.16* and Okteta installs libkasten3okteta1core.so*

To be able to fix this bug, I need an example to follow (i.e. another KF5 program or an explanation in one of KDE's wikis), preferably with instructions how to change the CMakeLists.txt files.
Comment 4 Andrew Crouthamel 2018-09-26 22:10:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Thomas Fischer 2018-09-27 07:05:15 UTC
Just checked how other KDE/KF5 programs handle their private libraries. Examples are taken from a current ArchLinux:

# pacman -Ql okteta | grep -E '[.]so$'
okteta /usr/lib/libkasten3controllers.so
okteta /usr/lib/libkasten3core.so
okteta /usr/lib/libkasten3gui.so
okteta /usr/lib/libkasten3okteta1controllers.so
okteta /usr/lib/libkasten3okteta1core.so
okteta /usr/lib/libkasten3okteta1gui.so
okteta /usr/lib/libokteta2core.so
okteta /usr/lib/libokteta2gui.so
okteta /usr/lib/qt/plugins/designer/oktetawidgets.so
okteta /usr/lib/qt/plugins/oktetapart.so

# pacman -Ql konsole | grep -E '[.]so'
konsole /usr/lib/libkdeinit5_konsole.so
konsole /usr/lib/libkonsoleprivate.so.18
konsole /usr/lib/libkonsoleprivate.so.18.08.1
konsole /usr/lib/qt/plugins/konsolepart.so

Unless (a) official KDE documentation recommends installing libraries at other locations and this recommendation is common consensus, or (b) there is a technical requirement to so (keeping KBibTeX's libraries in /usr/lib breaks things) and moving does not break anything, I won't change libraries' locations.

Please feel free to provide a patch for CMakeLists.txt files for distributions to use which wish to have different installation locations.