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, qu
Le dimanche 26 février 2006 à 14:07 +0100, Filippo Giunchedi a écrit :
> > 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 b
On Sun, Feb 26, 2006 at 04:17:29PM +0100, Josselin Mouette wrote:
> Wouldn't it more understandable with virtual packages? For example:
> python-bluez provides: python-bluetooth and conflicts: python-bluetooth
> python2.X-bluez provides: and conflicts: python2.X-bluetooth
if this is okay with pyth
3 matches
Mail list logo
