* Mathieu Malaterre <[email protected]>, 2014-06-03, 09:44:
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-runtime
[...]
If you have several shared libraries built from the same source tree,
you may lump them all together into a single shared library package
provided that all of their SONAMEs will always change together. Be
aware that this is not normally the case, and if the SONAMEs do not
change together, upgrading such a merged shared library package will be
unnecessarily difficult because of file conflicts with the old version
of the package. When in doubt, always split shared library packages so
that each binary package installs a single shared library.
[...]
Reading this section make me feel that lib such as:
$ readelf -d libvtkImagingColorPython27D-6.1.so.6.1.0
[…]
Should be removed from the package since the SONAME will change when
python 2.7 will not be the default python version (for example). Indeed
the SONAME contains the Python version (per upstream convention).
Formally, yes, all shared libraries that have Python-version-dependent
SONAME should be put in a package with a name that is also
Python-version-dependent. But practically, there won't be any new
version of Python 2.X[0], so it's only a concern if you plan switching
to Python 3.X.
[0] http://legacy.python.org/dev/peps/pep-0404/
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: https://lists.debian.org/[email protected]
