On Mo, 2010-12-06 at 18:29 +0100, Matthias Klumpp wrote: > Hi! > > PackageKit's aptcc backend currently misses install_files > > support. I suppose that : > > > > (1) I integrate the needed functions in APT, based on those > > currently written in Python (apt.debfile) > > (2) The PK backend calls the functions from APT > > > > The question now is what information is needed from APT for > > aptcc to work correctly. Information on this is appreciated. > This stuff needs to be implemented in APTcc, I think Daniel is already on > it, but he always likes help in developing the APTcc backend :P But we already have the code in python-apt, could move it to APT, and then call it from python-apt and aptcc.
> > > Alternatively, we could do this in aptcc itself; although this > > might lead to code duplication (if we do it in APT, we can change > > python-apt's apt.debfile to use the functions from APT and avoid > > the duplicate code). > > > > That part is important in order to port the file installation > > part of software-center to PackageKit, and to enable the session > installer > How do you mean? SC could use PK to do the installation, if APTcc supports > it... That's what I wrote. If we want a SC backend using PK, we need a PK backend supporting file installation. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
