dh_dbus

[Loïc Minier <lool@dooz.org>]

        Hi folks

 MFT: pkg-utopia-devel@ as I think we'd do the implementation

 Corsac (French Xfce DD) was saying on a French channel that he would
 like to introduce some "notification" virtual package post-lenny to
 allow to replace org.freedesktop.Notifications.service with different
 implementations and have conflicts etc.

 I suggested to go for something more generic: listing provided,
 depended on, and conflicting dbus services in misc:Depends,
 misc:Provides, and misc:Conflicts.

 e.g. a new dh_dbus would scan debian/avahi-daemon/etc/dbus-1/system.d
 for provided services and generate for example a
 dbus-org.freedesktop.Avahi entry in misc:Provides or a dbus-`md5sum
 org.freedesktop.Avahi` one, as well as the same entry in misc:Conflicts
 (since a service can only be provided once).
   We would have other packages with Dbus-Depends: org.freedesktop.Avahi
 set by the maintainer in control, and dh_dbus would make that a
 misc:Depends entry.

 What do you think?


 A sub question to solve is how to ensure a real package is set in
 dependencies.  One way is to require maintainers to do this, but
 another way which plays more nicely to derivatives is having real
 packages for these.  For instance, we would keep mappings between dbus
 service names and default distro implementation in the dbus source (or
 a new source) and would create binary packages such as for example
 dbus-notification-service package which would depend on
 notification-daemon | dbus-org.freedesktop.Notifications.service or |
 dbus-`md5sum org.freedesktop.Notifications.service`.

 (If we don't have a real package, a random implementation might be
 pulled depending of the order in which APT processes depends.)

   Bye
-- 
Loïc Minier