PolicyKit + KDE

Dario Freddi drf54321 at gmail.com
Wed Sep 2 00:51:07 BST 2009

On Wednesday 02 September 2009 12:16:07 am Andreas Pakulat wrote:
> On 01.09.09 23:03:47, John Tapsell wrote:
> > Hi all,
> >
> >   The problem is "make install" in kdelibs/kdebase  has traditionally
> > only installed files to your $KDEDIR directory.  However with
> > policykit requires files to be installed elsewhere.  For example
> > ksysguard now needs to install to:
> >
> > /etc/dbus-1/system.d/org.kde.ksysguard.processlisthelper.conf
> > /usr/share/dbus-1/system-services/org.kde.ksysguard.processlisthelper.ser
> >vice
> > /usr/share/PolicyKit/policy/org.kde.ksysguard.processlisthelper.policy
> >
> > To do so requires root privillages and modifies the main system - no
> > longer giving us the possibility of playing with one version of kde
> > which having another installed.
> So basically this means nobody except Gentoo people can build from sources
> as installing stuff in /usr/ will break packaging systems. IMHO thats not
> acceptable at all. PolicyKit _has_ to have a way of letting it load stuff
> from other places, if it doesn't its simply broken and we shouldn't use it
> at all.

PolicyKit is not broken, it's simply that installing and validate files that 
actually set your policies for root stuff in a location editable by a standard 
user woul make it broken for real.

That said, I like thiago approach. I will just spit out a warning

> Andreas, waiting some more with the next trunk-update until this mess is
> sorted.

More information about the kde-core-devel mailing list