Re: Handling python modules collision
On Tuesday, March 22, 2016 04:55:36 PM Frederic Bonnard wrote:
> Hi,
> I'd like your advises concerning the following situation : I'm packaging
> this python library :
> https://github.com/miguelgrinberg/python-socketio
>
> and I see that debian already provides a library with the same name :
>
> https://github.com/abourget/gevent-socketio
>
> The name can be changed of course but I'm not sure on how to deal with the
> fact that the first one wants to install in the same path i.e. :
> /usr/lib/python2.7/dist-packages/socketio
>
> Is that a proper case where to use "Conflicts" field ?
Only if they provide the same interface. Here are the relevant bit from
Debian policy:
10. Files
---------
10.1. Binaries
--------------
Two different packages must not install programs with different
functionality but with the same filenames. (The case of two programs
having the same functionality but different implementations is handled
via "alternatives" or the "Conflicts" mechanism. See Section 3.9,
`Maintainer Scripts' and Section 7.4, `Conflicting binary packages -
`Conflicts'' respectively.) If this case happens, one of the programs
must be renamed. The maintainers should report this to the
`debian-devel' mailing list and try to find a consensus about which
program will have to be renamed. If a consensus cannot be reached,
_both_ programs must be renamed.
I would recommend discussing this collision with both upstreams and see what
they say. It would be nice if one of them would rename.
Scott K
Reply to: