[Pkg-utopia-maintainers] Bug#572744: Shouldn't package be named coherence instead of python-coherence ?

[Olivier Berger]

Package: python-coherence
Version: 0.6.6.2-2
Severity: wishlist

Hi.

The current naming of the package seem to indicate that it provides some kind of python library to be used by other applications.

But it also provides a UPNP mediaserver AFAICT.

Is there a valid reason not to call it coherence ?

Or maybe provide two binary packages : one for the python low-level python components and one for the high-level coherence app (and applet) ?
The descriptions of packages would then reflect this as being less "framework" and more "end user app".

Thanks in advance.

Best regards,


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-coherence depends on:
ii  python                       2.5.4-9     An interactive high-level object-o
ii  python-axiom                 0.6.0-1     Python object database
ii  python-configobj             4.7.1-1     simple but powerful config file re
ii  python-gst0.10               0.10.18-1   generic media-playing framework (P
ii  python-louie                 1.1-1.1     Python signal dispatching mechanis
ii  python-pkg-resources         0.6.10-1    Package Discovery and Resource Acc
ii  python-support               1.0.6.1     automated rebuilding support for P
ii  python-tagpy                 0.94.7-1+b2 Python module for manipulating tag
ii  python-zope.interface [pytho 3.5.3-1+b1  Interfaces for Python

Versions of packages python-coherence recommends:
ii  libgdata-google1.2-1          2.28.2-1   Client library for accessing Googl
ii  python-mechanize              0.1.11-1.1 stateful programmatic web browsing

python-coherence suggests no packages.

-- no debconf information