GNOME-PackageKit packaging

[Julian Andres Klode]

On So, 2010-12-05 at 18:03 +0100, Josselin Mouette wrote:
> Le dimanche 05 décembre 2010 à 17:40 +0100, Matthias Klumpp a écrit : 
> > * 4 applications using the library:
> >               A. Package Manage   => low-level PM like Synaptic, using a
> > Debian-specific package-manager lib
> 
> As long as you need this one (and I think we all agree that it is badly
> needed), you need a Debian-specific way to do privileged operations,
> with the full APT interface in mind, not just a stripped-down version.
In APT2, the design I envision is a relatively thin layer (a system
module) for D-Bus that just forwards function calls via D-Bus to the
real module:

  Backend:      libapt + 'deb' system module
  D-Bus client: libapt + 'dbus' system module

> 
> >               B. Update Manager   => combination of -manager, -notifier,
> > can be based on PackageKit
> >               C. Software Center  => application-oriented version of A,
> > can use PK
> >               D. Software Sources => manages sources.list, can also use PK
> > 
> > (*) => Libpackagetool could use the PackageKit-daemon if possible,
> > otherwise, for example for searching the cache, it could use APT directly.
> > 
> > Would provide exactly the same stuff be reusing existing and well-tested
> > code. Why not improve PackageKit?
> 
> Because it just serves the purpose of adding an extra, useless layer.
> Once you have a powerful API that can do more and serve as a backend for
> a package manager, it can also do the simple things.
> 
> What we need is a generic way to encapsulate all operations available in
> libapt in a D-Bus interface, not to build a new extension to PackageKit
> every time someone recalls a feature APT has and yum has not.
> 
We need something like aptdaemon, but written in C/C++/Vala.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.