[packagekit] Debconf and PackageKit Was Re: Packagekit and Ubuntu

Daniel Nicoletti dantti85-pk at yahoo.com.br
Fri Feb 12 10:04:21 PST 2010

> setHints() sounds useful.
Actually Richard added this as we requested to pass the socket path for
debconf to use.

>   1. The client-side code starts up a process, or uses itself, on the
>   system bus which has an org.debian.Debconf interface (either at the
>   root or we pass the object path around with the DBus name).
>   2. It then calls setHints() with the unique name of the process on the
>   system bus.
>   3. Packagekit passes this on to the apt backend.
>   4. The apt backend arranges things such that debconf will use a dbus
>   frontend, set up to talk to this unique name.
>   5. When debconf needs input it attaches to the system bus and
>   communicates with the name that it knows is associated with this
>   transaction. If the name is not then when it does so then it can go
>   non-interactive.
>   6. When the client-side process attached to that name gets a request it
>   prompts the user and returns the results.
> That sounds feasible to me, with a couple of requirements:
>   * setHints() must only be allowed to be called by the owner of the
>     transaction.
good point not sure how it is today

>   * The client-side process only allows messages from root-owned
>     processes.
for this we add to /etc/dbus...something with a deny rule that will only
accept root

>   * The documentation for setHints() states "The following parameter
>     values are understood: [...]" so we should ensure that it doesn't
>     reject others. It would be simple to add another for our use though.
As this method was basically created for debconf I think it's easy to
extend to our needs

> Colin, Richard, does that sound ok to you?
> Thanks,
> James

Veja quais são os assuntos do momento no Yahoo! +Buscados

More information about the PackageKit mailing list