[Pkg-bluetooth-discuss] new packages in pkg-bluetooth svn

[Edd Dumbill]

On Mon, 2005-11-07 at 23:15 +0100, Filippo Giunchedi wrote:
> On Mon, Nov 07, 2005 at 09:53:58PM +0000, Edd Dumbill wrote:
> > We could provide some metapackages to deal with this, e.g.
> > 
> > bluetooth, Depends: bluez-utils (bluez-noninteractive-pin | bluez-pin)
> > bluetooth-desktop, Depends: bluetooth bluez-pin
> > 
> > With that configuration, we'd also want an /etc/alternatives setup for
> > the pinhelper, for which the GUI one overrides the non-interactive one
> > when installed.
> > 
> > A package named bluetooth also calms my worries about the LSB init

> but I would definitely ask debian-devel :)

Nah, no need :)

I quite like the scheme I proposed above, it's definitely more intuitive
and these days there's no doubt that BlueZ is the main contender.  When
I started out this work, there were 3 stacks to choose from.

Migrating init scripts is always a little troublesome, alas.  We need to
do some sort of postinst magic:

* if /etc/init.d/bluez-utils exists and hasn't been changed by the user,
then replace with /etc/init.d/bluetooth

* otherwise, display a notice to the user that they ought to merge
changes into /etc/init.d/bluetooth and remove /etc/init.d/bluez-utils

* if /etc/init.d/bluez-utils exists, then don't
execute /etc/init.d/bluetooth

Anyone got any better ideas about how to manage the transition?  I did
this sort of thing before with PAN.

-- Edd