[Pkg-bluetooth-maintainers] pybluez

[Filippo Giunchedi]

On Sun, Feb 26, 2006 at 01:46:43PM +0100, Michal Čihař wrote:
> > but yes, I would consider adding a python-bluetooth metapackage which depends on
> > python-bluez, just to be consistent with the recent bluez/bluetooth renaming
> > stuff.
> 
> If you want python-bluez, it should be reverse, quoting from Debian
> Python Policy:
> 
> A package with a name python-foo will always provide the module foo for
> the default Debian Python version of the distribution.

mmh that's tricky, CC'ing debian-python.

my rationale behind python-bluez is that bluez is not the only bluetooth stack
for linux, indeed the bluetooth metapackage is provided to support not only
bluez.
I'm not sure what is the right way to go for python-bluetooth, following the
same scheme as packages it would be:

python-bluetooth: depends python-bluez (and possibly others)
python-bluez: depends python2.3-bluez (or python2.4-bluez RSN)

this would require every python bluetooth stack binding to provide the
"bluetooth" module (thus honouring the python policy) and of course being
uninstallable at the same time (which IMO is fine, as one wants to use only one
bluetooth stack a time)

thanks,
filippo
--
Filippo Giunchedi
PGP key: 0x6B79D401
random quote follows:

What a strange illusion it is to suppose that beauty is goodness.
-- Lev Tolstoj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-bluetooth-maintainers/attachments/20060226/913054b7/attachment.pgp