Re: Proposed external dep: PolicyKit
- From: Murray Cumming <murrayc murrayc com>
- To: Matthias Clasen <matthias clasen gmail com>
- Cc: desktop-devel-list <desktop-devel-list gnome org>, David Zeuthen <david fubar dk>
- Subject: Re: Proposed external dep: PolicyKit
- Date: Wed, 07 May 2008 17:29:05 +0200
On Wed, 2008-05-07 at 11:23 -0400, Matthias Clasen wrote:
> On Wed, May 7, 2008 at 11:18 AM, Richard Hughes <hughsient gmail com> wrote:
> > I would like to propose PolicyKit[1] as an external dep for 2.26 - it's
> > mostly API stable[2], and is now being used as an optional dep in many
> > modules in gnome svn and HAL.
> >
> > I would like to depend on it for gnome-power-manager, and I hate all the
> > #ifdefs. Does anybody have any problems with PolicyKit being an external
> > dependency in 2.26?
> >
> > >From a user point-of-view PolicyKit rocks. It would be great if more
> > GNOME software could be comfortable using it upstream rather than being
> > patched by distros.
>
>
> Actually, the patches are using PolicyKit-gnome, too. If we allow
> dependencies on PolicyKit, we should allow PolicyKit-gnome, too, since
> it makes it very easy to write UIs that trigger privileged operations
> and handle all aspects of PolicyKit integration correctly.
Yeah. Direct use of the PolicyKit D-Bus API (as is currently necessary
from Python, for instance) is a bit strange, not documented, and is
apparently not really supported.
I haven't used PolicyKit-gnome but that should shield people from this.
I'd like to see python bindings for it.
--
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]