Hello
Porthole has some really good features, but I still run it as a luser. When I want to install something, Porthole executes 'sudo -p "Password: "' with the command it really wants as an argument thereof. In the preferences dialog, there's an option to change the command used, but this doesn't seem to have any noticeable affect (unless I'm looking in the wrong place).
I have a custom set of scripts that enable me to obtain rootly powers and would much prefer to use these instead of su/sudo.
So, this is a two stage thing really:
Why doesn't the configuration option have any affect? (Or, what does it really change?)
Please allow a configurable alternative to su/sudo.
I've had a quick look through the code, but I'm a Perl man and haven't yet delved into Python. The brief look I had suggested you're hard coding the use of 'sudo -p "Password: "', which is very bad technique. Then again, I might just be mis-reading things. :)
Dan
Logged In: YES
user_id=953915
Originator: NO
Yes, so far it is hard coded for the emerge commands. That will change in the next version, as well as being able to use pkgcore or paludis commands.
The preferences setting for su/gksu are for graghical clients to run outside scripts or programs as root.
Well, I worked about a week changing porthole to use seteuid/setegid, but theere were several parts of the code theat gtk specifically refused to work due to the detected seteuid. Most of the changes I had to revert.
Since gksu/gksudo is going the way of policykit, the options are more limited. Policykit seems to be becoming the prefered method, but it does not have a python interface except through d-bus. Going through another pygtk app that uses it, indicates it is not an easy task. It would also slow things down, which is not a problem for some things, but is for some portions of code.
I do have another idea that a small experiment seems to indicate will work, but will require at least python-2.6. But that will have to wait for yet another release.