GNOME-PackageKit packaging

[Julian Andres Klode]

On Sa, 2010-12-04 at 15:53 +0100, Julian Andres Klode wrote:

> On So, 2010-11-21 at 22:58 +0100, Matthias Klumpp wrote:
> > On Sun, 21 Nov 2010 18:45:58 +0100, Josselin Mouette <joss at debian.org>
> > > It is that bad. In squeeze we have software-center, update-notifier,
> > > update-manger and synaptic, with no less than 4 FUCKING ICONS in the
> > > administration menu, all about installing or upgrading software. 4 icons
> > > is 3 icons too many.
> > Agree.
> I do not agree here. Instead of creating one bloated application, it is
> much better to create multiple small ones.
Of course, you do not need 3 icons here, but can create one applications
that provides buttons: 
      * Manage Packages (experienced users only) 
      * Manage Software 
      * Update System 
      * Manage Software Sources

In any case, we need to ensure that we do not create monster
applications.

> > >> So there is no policy conflict between PK and Debian anymore, or do I
> > >> miss
> > >> something?
> > > 
> > > It’s not a problem of conflict or whatever. Again, I’d like to see a
> > > *consistent* software stack for package management. Having pieces of the
> > > stack based on the PK backend and others based on aptdaemon is not a
> > > long-term solution. Either we can base everything on aptdaemon, or we
> > > can base everything on PK - oh wait, the crippled PK interface doesn’t
> > > make this possible.
> > Okay, could you then please name the missing functionality? I'll talk to
> > Richard tomorrow explaining this. Usually, if there are good user cases and
> > if a change does not break existing stuff, he agrees adding more
> > functionality.
> And if not, you can add it yourself as the maintainer. For example, you
> could add a pk_package_get_debian_pin() to get the pin of a package.
> Just make sure that every function you add includes debian in its name.
> 
> Upstream may not like you for doing this, but that's a sane way to
> support our superior world correctly.
One thing I forgot: There is currently no way to query dependency
information via PackageKit, as far as I can tell.
-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

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