Hi, On Wednesday 18 March 2009 13:12:45 Olivier Crête wrote: > Hello, > > use.local.desc:app-admin/gnome-system-tools:policykit - Use > sys-auth/policykit to gain privileges to change configuration files > use.local.desc:app-admin/system-tools-backends:policykit - Use > sys-auth/policykit to gain privileges to change configuration files > use.local.desc:gnome-extra/gnome-lirc-properties:policykit - Use > sys-auth/policykit to gain privileges to change configuration files > use.local.desc:gnome-extra/gnome-power-manager:policykit - Enable > sys-auth/policykit authentication support > use.local.desc:media-sound/pulseaudio:policykit - Enable support for > PolicyKit framework. > use.local.desc:sys-auth/consolekit:policykit - Use the PolicyKit > framework (sys-auth/policykit) to get authorization for > suspend/shutdown. > > Feel the trend? gnome-base/gnome-panel will follow soon. Lets make this > global. Unless we decide that PolicyKit is the future and make it > compulsory). > > If no one complains, I will make the changes in a couple days.
I think it would be also good idea to add policykit support and finally unmask it. It seems some packages have hardcoded --without-policy-kit / --without- policykit and some others add policykit to package.use.mask (btw can it be unmasked by user from portage level??). I've been playing with policykit for a while now and never had any real problems with it. I would gladly help to support it by default. Thanks, Rob
signature.asc
Description: This is a digitally signed message part.
