PolicyKit + KDE

Dario Freddi drf54321 at gmail.com
Wed Sep 2 20:19:01 BST 2009

In data mercoledì 02 settembre 2009 20:53:34, Andreas Pakulat ha scritto:
> The problem is that some things where (are?) set to be installed outside of
> KDE's prefix, more importantly it tried to install into a location that is
> not writeable by an ordinary user. As kauth has (hopefully) gone through a
> review process before moving it to kdelibs it suggests that this was
> intentional because anything else wouldn't work with policykit. At least
> thats the thoughts I had.

KAuth was in kdereview for 3 weeks more than 2 months ago IIRC, so it's gone 
through quite a long review. Yes, the paths were intentional as otherwise the 
feature would not work, and *HINT*KDE has no policy regarding files that need 
a specific prefix*HINT*. KAuth is not the only one having this kind of 
problems: see python engine in KDEbase. So the problem is quite like: what do 
we need to do if some files require a specific path and do not work outside of 

> Hmm, a mv? Sorry thats not a solution, can polkit not be configured to find
> its policy files elsewhere than /usr? I'd really like to use the related
> features, but I'm not going to interrupt my packaging system for that (and
> moving stuff to /etc or /usr is exactly that).

AFAIK, polkit 0.9 cannot do that, at least not in the config files, there 
could be a build option. I suggest to report a feature request in PolicyKit 
)fd.o) defining the problem

> Maybe broken is a bit hard, incomplete might be better. I consider any
> software forcing me to screw with my packaging system to add something to
> it at least incomplete (tbh I consider it broken, but thats just my
> opinion).

The problem is not not letting people to install stuff elsewhere, it's more 
about security. Anyway the right route to take would be 1. having a policy for 
this kind of situations (check with kde-buildsystem) 2. eventually request a 
feature in polkit, if it does not support this in the very upcoming polkit 1.0 
(that actually should be in and ready for kde 4.4)


Dario Freddi
KDE Developer
GPG Key Signature: 511A9A3B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090902/80ac7044/attachment.sig>

More information about the kde-core-devel mailing list