https://bugzilla.redhat.com/show_bug.cgi?id=1887470 Jerome Marchand <jmarchan@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmarchan@xxxxxxxxxx --- Comment #5 from Jerome Marchand <jmarchan@xxxxxxxxxx> --- (In reply to Zamir SUN from comment #0) > RPMlint: > > libtraceevent.x86_64: E: no-ldconfig-symlink > /usr/lib64/libtraceevent.so.1.1.0 > libtraceevent-devel.x86_64: W: no-documentation > libtraceevent-devel.x86_64: W: dangling-relative-symlink > /usr/lib64/libtraceevent.so.1 libtraceevent.so.1.1.0 > > I'm trying to follow the way glibc separates package, so the real file stays > in libtraceevent while symlink goes to -devel. If this is not the suggested > way, I'd like to know the proper way for it. It's not a matter of real file vs symlink, it's a matter of versioned / unversioned shared libraries. The versioned libraries, against which programs are linked, belong to the main package. The unversioned libraries (as well as static libraries) belong to the devel package, because they are only needed when compiling. There is more info in the packaging guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/#_devel_packages So your %files section should contain %{_libdir}/libtraceevent.so.* and the "%files devel" section should contain %{_libdir}/libtraceevent.so Beside that, I didn't see anything wrong with the current spec file. I'm no packaging expert though. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
