<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Richard Hughes wrote:
<pre wrap="">On Fri, 2007-10-26 at 15:23 +0200, Tim Lauridsen wrote:
<pre wrap="">I have done a little thinking about what could be useful to have in the
packagekit backend API.
* get-group-list : Get a list groups found in the repositories.
To make it possible to make dynamic group view in a frontend client.
(search-group should be used to get the packages in the groups)
We already have this; see backend_get_groups:
backend_get_groups (PkBackend *backend, PkEnumList *elist)
g_return_if_fail (backend != NULL);
<pre wrap="">group<tab>categoryid;groupid<tab>translated categoryname;translated
groupname<tab>translated group describtion
We can't have any translations done by the daemon, they all have to be
enumerated types - the daemon has to be C locale, and the client
converts the enums to localised text. It's the same as what we do with
called text editors, these are programs that allow you to create and
edit files. These include Emacs and Vi."
The translations can be done in pk-common-gui.c in gnome-packagekit - we
can add as many translations and enumerated values there are you like. I
don't mind making the translators work harder :-)
The problem is in yum you have dynamic Category/Groups defined in a
comps.xml file loaded from the repositories.<br>
The comps files from different repos is joined into one category/group
The Category/Group contains a id and a descriptive name and a
translated names & decriptions all stored in the comps.xml files.<br>
These can not easily, be mapped to the enumerated groups used by
There translation is done in the comps files, so the backend dont need
to that translation, it just passes on the translation<br>