On 14/01/2011 19:42, Timothy Pearson wrote:
The reason for the third-party sudo is simply to
add /opt/kde3/bin and
friends to the built-in RPATH variable, thus allowing Trinity
applications
to be launched via "sudo<appname>", instead of "sudo
/opt/trinity/bin/<appname>". That's the only change; if you don't
trust
me grab the source of the official sudo package and the modified one and
run a diff between them. ;-)
It's been a while know that I trust you and I'm confident in your
project!
But at first, Trinity was a "non-identified project", that's normal! ;-)
As such, installation is optional but highly
recommended if you use sudo
often.
I do, so I need it.
A far better method would be to allow a
configuration file to add new
paths to an arbitrary location within the RPATH variable (thus not
requiring a recompiled version of sudo), but I don't think that will
happen for a long time, if ever.
Hope this helps clear up some of the confusion!
Yes, thank you for the very clear explanations.
Maybe another to do the job would be to use an alias such as
alias sudo='RPATH=$RPATH:/opt/trinity/bin /usr/bin/sudo'
or something like that...?
I wish I could. The problem is that sudo, at least under Ubuntu and if I
remember correctly Debian as well, does not allow any environment variable
or configuration file to change its compiled-in RPATH (probably for
security reasons).
Tim