On Fri, 2019-04-05 at 09:04 +0000, John Paul Adrian Glaubitz wrote:

Hello!

I am updating the bochs emulator package from the Emulators project as a small exercise. The emulator now ships with plugin files which rpmlint recognizes as development files and complains about them:

[ 42s] bochs.x86_64: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib64/bochs/plugins/libbx_acpi.so [ 42s] bochs.x86_64: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib64/bochs/plugins/libbx_biosdev.so [ 42s] bochs.x86_64: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib64/bochs/plugins/libbx_cmos.so (...) [ 42s] bochs.x86_64: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib64/bochs/plugins/libbx_vga.so [ 42s] bochs.x86_64: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib64/bochs/plugins/libbx_x.so [ 42s] A file that is needed only e.g. when developing or building software is [ 42s] included in a non-devel package. These files should go in devel packages.

Can anyone tell me what the proper way of handling plugins in an RPM package is? Should I move these files into a separate -plugin package?

The problem seems to be that those are symlinks - which makes the rpmlint barf. If it's plugins, they should be built with -module -avoid-version and rpmlint won't complain. Cheers Dominique