[arch-dev-public] GNOME 2.28 roadmap

Jan de Groot jan at jgc.homeip.net
Tue Oct 6 05:48:50 EDT 2009


On Tue, 2009-10-06 at 11:16 +0200, Jan de Groot wrote:
> On Tue, 2009-10-06 at 10:57 +0200, Pierre Schmitz wrote:
> > Am Dienstag 06 Oktober 2009 10:38:53 schrieb Pierre Schmitz:
> > > nonoptional
> > 
> > To clrafiy this: it might be possible to build KDE without policykit with loss 
> > of functionality and we sould need to drop some packages like shaman and k3b.
> 
> This is the fedora discussion:
> http://www.linux-archive.org/fedora-development/358521-policykit-0-9-going-away.html
> 
> Their KDE project meeting about it:
> http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2009-09-01
> 
> Another related bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=519674
> 
> It appears the only authorization agent at this moment is the one
> provided by polkit-gnome, so the "OnlyShowIn" should not be limited to
> GNOME only as stated by the bugreport.

Looking further, there's a polkit1 branch of polkit-qt, though it's far
from complete. This is what KDE has to say about Polkit1:
http://techbase.kde.org/Polkit-Qt-1

As we'll lock out software from our distribution if we remove policykit
now, I think it's best to keep policykit for KDE. When KDE 4.4 is
released, I think it's safe to remove and use polkit instead.

Plans as we have them now are to remove PolicyKit 0.9 support from
anything that isn't KDE related. This means that GNOME will lose the
authorization agent and the policykit settings gui. As policykit is only
used by KDE applications when GNOME 2.28 comes into the repositories, I
don't see a problem using the KDE tools for that.





More information about the arch-dev-public mailing list