On 11/04/2010 12:52 PM, Duncan Mac-Vicar P. wrote:
This was the approach we had with the old GHNS where we used static xml files for the package data. Now KDE switched to OCS as real REST based client/server protocol where more interactive features are possible.
I think OCS is the more powerful approach.
Sure, for the appstore I think something like GHNS is the way to go. However we use PackageKit for the updates (as an applet), and it would be good to have it integrated as well, so that if an update comes, and there is appdata for it, you see the update as one app.
What do you think?
btw, Daniel Nicoletti (KPackageKit developer) is also very open to integrate the Application support so it can also use the OCS API directly in addition to the desktop.db thing. So we could start with a helper to pull some app data from OCS into desktop.db while KPackageKit gets real OCS support. At least it would solve our problem of a friendly updater. The need for a packagekit based updater is that we have features like notifications of patch messages, distribution upgrade notifications and start of the dist-upgrade workflow, etc. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org