Quote Originally Posted by anda_skoa View Post
Actually it might be even better to check if, e.g. write access, is allowed on the target directory.
The user might not be superuser or not running the process with superuser priviledges but might still have write permissons due to being a member of the group owning the directory.
Cheers,
_
Actually I do that for the selected installation directory, and it works fine. On the command prompt if I start the installer with sudo ./setup it will install the icons and desktop.entry file as wanted, so that seems at the moment to be the only way... I also set file permissions afterwards (for all installed files) to be of owner user instead of owner root. But that still doesn't satisfy my need for incidental elevation of user rights. I'd prefer the setup fase A (collection of information) to be with normal user rights and ONLY Face B - the worker, (and ONLY for saving the icons and desktop.entry file) to have elevated rights. This would keep the security hole tight and also be considered proper use. I am reading the policyKit while typing but that seems to be a lil over the top....