Il 19/12/2015 15:02, Björn Esser ha scritto:
Am 19.12.2015 um 14:11 schrieb Mattia Verga:
While checking rpms for a new package with rpmlint I encountered the error: libpasastro.x86_64: E: no-ldconfig-symlink /usr/lib64/libpasplan404.so.1.0
Now, packaging guidelines doesn't say anywhere (or at least I was unable to find it) that symbolic links to soname must be installed by the package instead of rely on ldconfig calls for creating and removing them when installing and uninstalling the package.
Since the upstream maintainer wants to rely on ldconfig and doesn't want to ship the symbolik links, can the package be submitted for review as is, or I must edit the sources to fix that error?
You can easily fix that error by creating a symlink during %install and include that into the %files of the package, like this:
On top of the spec-file:
%global sover 1
…
%install # Install the built binaries.
ln -fs %{_libdir}/libpasplan404.so.%{sover}.0 \ %{buildroot}%{_libdir}/libpasplan404.so.%{sover}
…
%files # doc-files, license, other files %{_libdir}/libpasplan404.so.%{sover}*
If the SO-version changes during an update, build will fail, because of installed, but not packaged files; so you don't miss to adjust the value properly and the symlink won't dangle then.
Cheers Björn -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Thank you, the %{sover} trick is a great workaround!
Mattia