On Fri, 29 Jul 2016 at 11:00:52 +0100, Paul Sladen wrote:
> Previous packaging working had been done since 2009, and published
> in the APT repositary documented at:
>
> http://soft.g-vo.org/repo
> http://vo.ari.uni-heidelberg.de/debian
>
> Thus, despite this being the initial upload to Debian itself, to
> likely makes sense to follow the package name and changelog in the
> existing source packages.
If you would "import votable" then I would recommend using binary package
names python-votable and/or python3-votable, perhaps with some
Provides/Breaks/Replaces on the name that exists outside Debian.
(I did the same recently for src:tap.py, python-tappy -> python-tap,
although I didn't add the Provides there.)
The source package can still be whatever you think is best.
The naming policy for Python packages is intended to work like the
naming policy for C library SONAMEs: it makes incompatibilities and
conflicts as obvious as possible. If someone else packages a module
named "votable" for some reason (perhaps election-related), the fixed
naming makes it extremely obvious that there is going to be a problem.
S
