Le 26/11/2011 17:30, Kristopher John Gamrat a écrit : > On Saturday 26 November 2011 11:15:19 am Calvin Morrison wrote: >> Hello, >> >> I think another thing on all of our minds should be towards dealing with >> the problems related to sudo. As we know not all distros support it, and >> also removing sudo in cases can remove the entire trinity install, wreak >> havoc and other terrible things. >> >> Do we have a plan for this? Tim what needs to be done? > > Some people don't even use sudo, and not all distros use it, even if they have it installed by default. > > I don't think sudo should be a dependency. > > Also, why does trinity have it's own sudo? I'd think it should be able to find it in $PATH? I agree with you and I have no answers to your questions. I saw it's needed because of a problem with the path but I don't fully understand. I tried Debian defaults in /etc/sudoers: Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" without noticing problems. Maybe trinity could only change /etc/sudoers (with debconf), adding: Defaults secure_path=/usr/local/sbin:/usr/local/bin:/usr/sbin:/opt/trinity/bin:/usr/bin:/opt/trinity/sbin:/sbin:/bin:/usr/X11R6/bin if it's really important. Or maybe it could install its own version of sudo in /opt/trinity/bin, with a different configuration file (/etc/sudoers-trinity, for example), without conflicting with the installed one. Does somebody knows what can be done to test sudo installation? -- Laurent Dard