GNOME-PackageKit packaging

Matthias Klumpp matthias at nlinux.org
Sun Dec 5 17:09:26 UTC 2010


On Sun, 05 Dec 2010 18:10:37 +0100, Julian Andres Klode <jak at debian.org>
wrote:
> APT pinning is a feature for advanced users only and should not be
> exposed in the frontends. You cannot do useful things with it in the
> frontend anyway. But there are other problems:
> 
>       * 'Software Sources' does not allow editing of sources
>       * Bug#606025: packagekit: Does not support conffile
>       * How will multi-arch and tdebs work once they are there?
>       * PackageKit hatred in general
Huh? PackageKit allows editing of software-sources, or do I missunderstand
you there? A prober place to fix Bug#606025 would be in dpkg, but I
recently talked to the APTcc maintainer who said it would be trivial to
implement a workaround in APTcc by using Debconf.
For multi-arch debs PackageKit already provides the required
infrastructure, but better talk to Richard. If there's a good reason from
user-perspective to add a feature, he will allow it. It is also easy to
include some more APT-features, if they don't break other backends or
clutter the API. (openSUSE and the Foresight people do this already)
For the last point I don't have a solution... These people should try
PackageKit on multiple distributions or look at the current API. (Of course
there are negative points, but instead of helping people like Daniel to
improve the APTcc backend, more and more tools are created. APTd copied a
lot of the PackageKit API and Muon even uses some of the KPK GUI code and
APTcc parts)
Cheers
  Matthias




More information about the pkg-gnome-maintainers mailing list