[packagekit] [PATCH 3 of 4] Add progress reporting to pisi backend

Ikey Doherty ikey at solusos.com
Sat Jun 8 06:40:00 PDT 2013

On 08/06/13 14:31, Matthias Klumpp wrote:
> Hi!
> Without knowing the Pisi backend, your patches look okay in general.
> It might make sense to use the PackageKit GIR interface in some places
> instead of python-packagekit, but since I never wrote a Python PK
> backend, I don't have much experience here (I'll leave this up to
> Richard to comment :P).
> Do you plan to maintain the Pisi backend in future?
> Cheers,
>      Matthias
Hi Matthias!
That could definitely be a plan for the future, switch it to GIR 
interface. Right now I can see that several key features were always 
missing from the PiSi backend.
What I'd like to add:
  * Download support (done via the pisi.api.fetch, similar to how I'm 
handling install)
  * Support reboot, etc,
  * Pull CVE's and BUGID's from <Comment>'s in pisi-index
  * Speed it all up :)

I would like to maintain the PiSi backend, its something we intend to 
integrate quite deeply within SolusOS 2. That said a decision would have 
to be made on which PiSi to follow :)

PiSi itself (the original Pardus version) is no longer maintained, as 
Pardus switched to Debian as a base. Within SolusOS we intend to 
actively maintain our version of PiSi, and hopefully make it a standard 
implementation. My thought on this topic is that nobody else is 
maintaining or adding significant fixes/features to any implementation 
of PiSi but our own, so I naturally propose the SolusOS PiSi 
implementation to become the reference standard (I say this because we 
intend to add further PackageKit-friendly features, such as mimetype 
providers and searching, into our PiSi implementation)


Ikey Doherty
  - SolusOS Founder

More information about the PackageKit mailing list