Alec Leamas wrote:
Still a newbie I have repeatedly been running into apps which stores
private, unversioned libraries into /usr/lib*. The usual symptom is
'invalid-soname' errors rpmlint errors.
There's no requirement that our packages have no errors from rpmlint. As far
as I know, invalid-soname does not match any requirement in our packaging
guidelines. Unversioned shared libraries are bad, but inventing a library
version can lead to conflicts with future upstream releases for public
libraries, and is just not worth it at all for private ones. There's no need
for a soname version if the library comes from the same package as the only
user(s) of it.
Kevin Kofler