[packagekit] Configuration files for backends

Richard Hughes hughsient at gmail.com
Thu Jun 18 03:18:31 PDT 2009


On Thu, Jun 18, 2009 at 11:09 AM, Valeriy Lyasotskiy<onestep at irc.lg.ua> wrote:
> On Thu, 18 Jun 2009 10:49:57 +0100
> Richard Hughes <hughsient at gmail.com> wrote:
>
>> Is the logic that the foo backend will access /etc/PackageKit/foo.conf?
>
> Not neccesary, it may be single file /etc/PackageKit/Backend.conf and it may contain [dummy], [alpm], [apt] sections and [alpm:mapping], [apt:gpgconfig] subsections.

I don't really want a generic Backend.conf -- it's open to too much abuse.

> It just will make configuration system for all the backends unified. But if we stick to using /etc/PackageKit/${backend_name}.conf, then, surely, GKeyFile makes sense.

I think the backend config being separate is a very good thing, as it
allows distributors to split PackageKit up into sub-packages, for
instance PackageKit-backend-smart and PackageKit-backend-zypp. A
combined store would make that very difficult.

I think the way you want to do this is use GKeyFile and then stick a
few files in /etc/PackageKit.

Just make sure you install them in Makefile.am too :-)

Richard.



More information about the PackageKit mailing list