[gobolinux-devel] [gobolinux-commits] tools/Scripts/bin CommandNotFound
Lucas C. Villa Real
lucasvr at gobolinux.org
Mon Feb 25 19:44:56 NZDT 2008
On Sun, Feb 24, 2008 at 10:35 PM, Michael Homer <michael at gobolinux.org> wrote:
> On Mon, Feb 25, 2008 at 7:27 PM, Jonas Karlsson <jonka750 at student.liu.se> wrote:
> > On Sun, 24 Feb 2008 23:56:30 +0100, Michael Homer <michael at e.geek.nz> wrote:
> >
> > > CVSROOT: /sources/goboscripts
> > > Module name: tools
> > > Changes by: Michael Homer <mwh> 08/02/24 22:56:30
> > >
> > > Modified files:
> > > Scripts/bin : CommandNotFound
> > >
> > > Log message:
> > > Offer Compile for executables found in multiple programs too. More comments.
> > [...]
> >
> > > log('You can install one of these by typing (for example):')
> > > log(' sudo InstallPackage %s'%(packages[0]))
> > > + log('or')
> > > + log(' sudo Compile %s'%(packages[0]))
> > > else:
> > > log('The program "%s" is not currently installed. You can install it by typing:'%(cmd))
> > > log(' sudo InstallPackage %s'%(packages[0]))
> >
> > You shouldn't recommend using sudo with the tools. They take the
> > appropriate level of autorization they need when they run. Actually
> > I've seen sudo breaking Compile due to environment reset.
> Good point. Ok then, fixed.
>
> While we're on the subject, though, I think we should add "Defaults
> !env_reset" to sudoers. The way we set it up, it doesn't add any sort
> of security, it's just a hassle and a hurdle. If somebody genuinely
> wants to do that for some reason, they'll know how to change their
> configuration.
It's already there in the latest version of the recipe (014 ships with
that option on).
--
Lucas
powered by /dev/dsp
More information about the gobolinux-devel
mailing list