| 1 |
On Thu, Mar 19, 2009 at 10:26 AM, Rémi Cardona <remi@g.o> wrote: |
| 2 |
> Le 19/03/2009 15:23, Robert Piasek a écrit : |
| 3 |
>>> |
| 4 |
>>> Feel the trend? gnome-base/gnome-panel will follow soon. Lets make this |
| 5 |
>>> global. Unless we decide that PolicyKit is the future and make it |
| 6 |
>>> compulsory). |
| 7 |
>>> |
| 8 |
>>> If no one complains, I will make the changes in a couple days. |
| 9 |
> |
| 10 |
> That seems reasonable. ACK from me. |
| 11 |
> |
| 12 |
>> I think it would be also good idea to add policykit support and finally |
| 13 |
>> unmask |
| 14 |
>> it. It seems some packages have hardcoded --without-policy-kit / |
| 15 |
>> --without- |
| 16 |
>> policykit and some others add policykit to package.use.mask (btw can it be |
| 17 |
>> unmasked by user from portage level??). |
| 18 |
>> |
| 19 |
>> I've been playing with policykit for a while now and never had any real |
| 20 |
>> problems with it. I would gladly help to support it by default. |
| 21 |
> |
| 22 |
> It's unfortunately not that simple. Some applications require very little |
| 23 |
> from PK (the clock applet from gnome-panel is one of those iirc). |
| 24 |
> |
| 25 |
> But some others (I'm looking at you, gnome-power-manager) just fail |
| 26 |
> miserably if a specific policy file isn't installed. So for each package |
| 27 |
> that uses PK, we need to come up with a default policy file that fits with |
| 28 |
> Gentoo tradition. |
| 29 |
> |
| 30 |
> Bottom line, none of us took the time to do this because we just didn't have |
| 31 |
> the time to take care of this. We could definitely use some help to figure |
| 32 |
> out what to ship as "reasonable" defaults to our users. |
| 33 |
> |
| 34 |
> Cheers, |
| 35 |
> |
| 36 |
> Rémi |
| 37 |
> |
| 38 |
> |
| 39 |
|
| 40 |
The problem would be a simple fix if PolicyKit supported groups and we |
| 41 |
could just say "give all access to those in the wheel" group as a |
| 42 |
reasonable default. But alas, it does not. Arguably we can probably |
| 43 |
patch that in and just be done with it. |
| 44 |
|
| 45 |
Unless someone has some better ideas for a reasonable default. (IMHO, |
| 46 |
removing all of PolicyKit is a reasonable default but it looks like |
| 47 |
going forward GNOME is just using it without really any documentation |
| 48 |
or any forethought into the real world implications of PolicyKit and |
| 49 |
the inherent support/issues with ConsoleKit) |
| 50 |
|
| 51 |
-- |
| 52 |
Doug Goldstein |
Archives