[packagekit] initial work on the apt dbus backend

[Owen Taylor]

On Wed, 2008-02-13 at 14:59 -0500, Robin Norwood wrote:
> > > Since PACKAGEKIT_DBUS_INTERFACE is different per-backend, I'm not
> > > sure if there's a pythonic way to abstract that into a base class,
> > > but keep the PACKAGEKIT_DBUS_INTERFACE constant per-child-class.
> > > Anyone with python skills know?  That way most of the signals could
> > > just go in the base class, like the old yum/python backends.
> > 
> > That could rock.
> 
> Been talking to Owen here at RH about it, and he doesn't see an easier
> way.  I hate to have all this cargo-culted code, but the way the dbus
> decorators are written we may have to live with it.

I think there's a bit of D-BUS abuse going on here. All the backends
export the same *interface* (a D-BUS interface isn't that different
from a Java/GObject/etc. interface after all.) They rather should
correspond to different well-known bus names.

- Owen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/packagekit/attachments/20080213/0dcc02cc/attachment-0004.pgp>