(Moving discussion of sudo-trinity to a new thread.)

On Fri January 14 2011 10:42:59 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. ;-)

$ diff -r sudo-1.7.4p4/ sudo-trinity-1.7.2p7/ | wc -l 112770

Would it be possible to have kde-core-trinity depend on sudo, and to have sudo-trinity conflict with sudo and provide sudo?

This would allow people to retain Debian's sudo if they prefer.

--Mike Bird

I suppose that would be an acceptable solution, barring any unforeseen problems. Before I implemented the sudo-kde3/sudo-trinity system, I was receiving constant bug reports about Trinity applications not working with sudo, so you can understand my reluctance to alter the packaging at this point.

I wish Debian would consider the merits of a separate configuration file for sudo though, as right now it forces me to say "pick your poison"--either Trinity won't work properly (especially in kcontrol), or you have to use have a possibly less secure sudo (although this is somewhat unlikely).

Tim