[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: rpmlint warnings...

On Sun, 15 Nov 2009 22:30:44 +0100, Dominik wrote:

> On Sunday, 15 November 2009 at 21:59, Nathanael Noblet wrote:
> > Hello,
> >   So I recently posted my first package and the review. While I waited I started cleaning up more issues I found after I realized you could run rpmlint on the actual rpm and not just the spec file. I'd like the review to go as quickly as possible so I'm just trying to get all those warnings cleaned up.
> > 
> >   My package has a number of sub packages for various backend drivers. These subpackages basically contain a .so file for the most part however I'm getting rpmlint messages as follows
> > 
> > libdspam.x86_64: W: devel-file-in-non-devel-package /usr/lib64/libdspam.so
> > 
> > how is libdspam.so determined to be a devel file?
> Shared objects (libraries) residing in %{_libdir} usually have names like
> libfoo.so.X.Y.Z where X.Y.Z is their ABI version number. -devel subpackages
> contain libfoo.so which is usually a link to libfoo.X.Y.Z and is used for
> linking against libfoo (-lfoo in linker command line).
> > libdspam.so.7.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped
> > 
> > Is what I get back from file. What is it that I'm missing?
> Judging by the above, your libdspam.so should in fact be named
> libdspam.so.7.0.0.

It is. "file" prints the file name, not the SONAME.

Often, projects, which dlopen plugin/module shared libraries at run-time,
store the versioned libraries as well as the .so symlinks. Then they dlopen
the libraries via the .so symlinks.

Find out how and with what file names those backend libraries are loaded.
If the .so symlinks are not needed, don't package them. And if the
backend libraries have SONAMEs defined, check for [potential] conflicts with
system libraries.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]