On Monday 20 October 2003 20:22, Buchan Milne wrote: > I am packaging some amateur radio software, a number of the packages > depend on hamlib, so I have packaged that too. > > However, hamlib ships with some plugins, and I don't seem to find a > solution that rpmlint agrees with. So, I have these packages: > > > $ rpm -qlp libhamlib1-1.1.4-1mdk.i586.rpm [ .. skip .. ]
> It looks like rpmlint is wrong, since: > -this is not a library package > -the so names look ok? > > So, is this a problem with the source package (should these be > /usr/lib/hamlib-version/<plugin>.so, or is rpmlint just being too > picky? i guess it is too picky. E: hamlib-plugins invalid-soname /usr/lib/hamlib-dummy.so rpmlint check that file under /lib, ending in .so, are real library. a library must provide a soname, ( obtained by objdump, i think ). Without it, this is a error, since the dynamic loader won't be able to find it. But, since this is not a library, this is wrong. E: hamlib-plugins non-versioned-file-in-library-package /usr/lib/hamlib-yaesu.la Since the plugin are not executable or valid library ( .so ), rpmlint think it is some kind of data, and so, they should be in a specific versioned dir, in order to have library installed side by side. rpmlint think this is a library, because it put some file in */lib, ending with .so. You cannot put the plugin under share, since share should be used for architecture independent files. So, i think this should be added as an exception, or to have some directory for .so files without soname. by the way, are .a needed for plugins usage ? I thinked that it was used for static linking, and so, this belong to -devel package, no ? -- Micha�l Scherer
