2017-07-17 07:00:02 UTC
Hi Michael. I don't agree with renaming the package name. The debian
policy manual says in section 8.1  that:
The run-time shared library must be placed in a package whose
nameÂ changes whenever the SONAME of the shared
Â Â Â Â Â Â Â library changes.Â Â This allows several versions of the shared
Â Â Â Â Â Â Â library to be installed at the same time, allowing installation
ofÂ the new version of the shared library without immediately
breakingÂ binaries that depend on the old version.Â Â Normally,
the run-timeÂ shared library and its SONAME symlink should be
Â Â Â Â Â Â Â placed in a package named librarynamesoversion,Â where soversion
is the version numberÂ in the SONAME of the shared library.
Â Â Â Â Â Â Â Alternatively, if it would be confusing to directly append
Â Â Â Â Â Â Â soversion to libraryname (if, for example, libraryname itself
ends in a number),Â you should use libraryname-soversionÂ instead.
This is what I believe we are doing. Can you explain more in detail
what is wrong? From my reading, we are doing what we should do, and
what you suggest would not be consistent with the above.