[opensuse-packaging] Rpmlint says that package does not provide any libraries, but it does!
Hi. I am trying to build a package home:rwman:branches:multimedia:apps/suil Rpmlint throw a warning: [ 27s] RPMLINT report: [ 27s] =============== [ 28s] libsuil-x11-in-qt4.x86_64: W: shlib-policy-missing-lib [ 28s] libsuil-x11-in-gtk2.x86_64: W: shlib-policy-missing-lib [ 28s] libsuil-gtk2-in-qt4.x86_64: W: shlib-policy-missing-lib [ 28s] libsuil-qt4-in-gtk2.x86_64: W: shlib-policy-missing-lib [ 28s] Your package starts with 'lib' as part of its name, but does not provide any [ 28s] libraries. It must not be called a lib-package then. Give it a more sensible [ 28s] name. All these packages do have a .so file (it's all it have actually) - so why rpmlint gives the warning? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wednesday 2015-11-25 23:49, Roman Evstifeev wrote:
For some easy cases, rpmlint is badly positioned. (Like "libreoffice".) For some hard cases, there is no generic solution. One can teach rpmlint to specifically ignore libXXX-tools, but then someone may start making a libXXX-data. You can ignore that too, and then someone makes libXXX-somethingelse. If you know you have the shlib guideline right, and reviewers concur, then just ignore rpmlint when it comes to that warning. The other option is to spend a hackday on rpmlint making it more intelligent ;-) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi, On Thu, 26 Nov 2015, Roman Evstifeev wrote:
Does it only have *.so files, not *.so.* files? If so, that's not usual names for shared libraries, but rather for plugins (and if it's plugins the package indeed shouldn't be called libFOO). If it's real shared libraries (supposed to be linked to other programs by ld) then the program author of that didn't think about versioning (how to call the next version of libfoo.so, if the first version wasn't named libfoo.so.1?). In the unlikely case that this really is as intended you can ignore the warning. Looking at the buildlog the package installs these files into e.g. /usr/lib64/suil-0/libsuil_qt4_in_gtk2.so That's not a shared library path either, and from that fact and file naming this really seems just a normal plugin loaded by something else at runtime. Don't name your packages lib* in that case (on idea would be suil-plugin-qt4-in-gtk2). Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wednesday 2015-11-25 23:49, Roman Evstifeev wrote:
For some easy cases, rpmlint is badly positioned. (Like "libreoffice".) For some hard cases, there is no generic solution. One can teach rpmlint to specifically ignore libXXX-tools, but then someone may start making a libXXX-data. You can ignore that too, and then someone makes libXXX-somethingelse. If you know you have the shlib guideline right, and reviewers concur, then just ignore rpmlint when it comes to that warning. The other option is to spend a hackday on rpmlint making it more intelligent ;-) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi, On Thu, 26 Nov 2015, Roman Evstifeev wrote:
Does it only have *.so files, not *.so.* files? If so, that's not usual names for shared libraries, but rather for plugins (and if it's plugins the package indeed shouldn't be called libFOO). If it's real shared libraries (supposed to be linked to other programs by ld) then the program author of that didn't think about versioning (how to call the next version of libfoo.so, if the first version wasn't named libfoo.so.1?). In the unlikely case that this really is as intended you can ignore the warning. Looking at the buildlog the package installs these files into e.g. /usr/lib64/suil-0/libsuil_qt4_in_gtk2.so That's not a shared library path either, and from that fact and file naming this really seems just a normal plugin loaded by something else at runtime. Don't name your packages lib* in that case (on idea would be suil-plugin-qt4-in-gtk2). Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Jan Engelhardt -
Michael Matz -
Roman Evstifeev