On Wed, Feb 10, 2010 at 1:19 AM, Debarshi Ray <[email protected]> wrote: >> Now think on the great part of this things. >> If we define a standard ontology to use for this use case, packagekit >> can become a simple tool > > PackageKit is actually quite simple. It is nothing but a daemon which > provides a standard D-Bus interface which front-ends like pkg-con, > gnome-packagekit, KPackageKit, and even some applications and > libraries (GStreamer, Anjuta, etc.) use. The daemon hands over all the > work to the distribution's package/repository manager (eg., RPM/YUM, > RPM/Zypp, dpkg/APT, etc..) > >> And any distro should only write a simple miner, >> and it became packagekit friendly. > > With PackageKit's current design, writing a backend is just a matter > of implementing the various operations supported by the D-Bus > abstraction in terms of the distribution's packaging system and the > distribution already has a package/repository manager. >
yes, yes, maybe i'm a bit too exited on the idea, and talking with fabio that has just wrote the entropy-packagekit plugin i'm fantasticating about this kind of thing. as wrote before we won't substitute the package/repo manager at all, but only try to provide a standard, integrated way of storing apps info. [where tracker are available] Michele -- michele tameni _______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
