1 |
On Fri, 2 Oct 2009 00:54:50 +0100, Stroller wrote: |
2 |
|
3 |
> > I think you need to re-read the ebuild. sudo depends on virtual/ |
4 |
> > editor, |
5 |
> > not nano. Nowhere is nano hardcoded to be a requirement of sudo. On |
6 |
> > the |
7 |
> > other hand, if you went with the upstream settings, you'd need to |
8 |
> > add vim |
9 |
> > as a dependency, even for those that don't wish to use it. Forcing |
10 |
> > such |
11 |
> > things on the user is most definitely not the Gentoo Way. |
12 |
> |
13 |
> You appear to be demonstrating that you don't fully understand the |
14 |
> problem: |
15 |
> |
16 |
> 828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild |
17 |
> # XXX: /bin/vi may not be available, make nano visudo's default. |
18 |
> --with-editor=/bin/nano \ |
19 |
|
20 |
How so? That config option for sudo sets the DEFAULT editor, what to use |
21 |
if nothing is defined in the config file or environment variable. That's |
22 |
what both my text and the portion of the ebuild that you have quoted |
23 |
state. It in no way forces the use of nano in order to use visudo. If |
24 |
that were the case, DEPENDS would specify nano instead of accepting |
25 |
virtual/editor. |
26 |
|
27 |
visudo is not hard coded to use nano, or even $EDITOR, you can set it to |
28 |
use whatever you want. The ebuild merely makes sure the default tallies |
29 |
with the default for $EDITOR. |
30 |
|
31 |
|
32 |
-- |
33 |
Neil Bothwick |
34 |
|
35 |
I have plenty of talent and vision. I just don't give a damn. |