On 2016-05-11 22:13, Ole Streicher wrote: > Christian Kastner <ckk@debian.org> writes: >> On 2016-05-11 03:41, Benda Xu wrote: >>> I am packaging a library called "casacore" which provides >>> libcasa_python3.so.2 and libcasa_python.so.2 >>> with SONAME=2. >>> How should them be named when the python major version and SONAME could >>> cause confusion? > >> According to the Debian Python Policy [1] and assuming from [2] that the >> module name is "casacore" > >> [2] http://casacore.github.io/python-casacore/ > > That is another package. As far as I understand it, the libraries > mentioned by Benda are just some data type converters; they don't > contain an importable module. The package in [2] is built on top of this > library (but a package that is built independently), and this should > ofcourse get the name given in the policy. > > The library Benda speaks about is not covered by the Python Policy, but > a normal shared library that should be covered by the standard Debian > Policy. I should have looked into it more. Thank you for correcting me! Regards, Christian
Attachment:
signature.asc
Description: OpenPGP digital signature