| 1 |
>> You appear to be demonstrating that you don't fully understand the |
| 2 |
>> problem: |
| 3 |
>> |
| 4 |
>> 828 ~ $ grep nano /usr/portage/app-admin/sudo/sudo-1.7.2_p1.ebuild |
| 5 |
>> # XXX: /bin/vi may not be available, make nano visudo's default. |
| 6 |
>> --with-editor=/bin/nano \ |
| 7 |
> How so? That config option for sudo sets the DEFAULT editor, what to use |
| 8 |
> if nothing is defined in the config file or environment variable. That's |
| 9 |
> what both my text and the portion of the ebuild that you have quoted |
| 10 |
> state. It in no way forces the use of nano in order to use visudo. If |
| 11 |
> that were the case, DEPENDS would specify nano instead of accepting |
| 12 |
> virtual/editor. |
| 13 |
|
| 14 |
Agree. There's no need in making vim as depends. But in other hand in |
| 15 |
vanilla sudo |
| 16 |
package there's VI hardcoded by default. And MOST if not ALL users who |
| 17 |
have VIM |
| 18 |
installed on their shiny Gentoo systems expect that VIsudo will behave as |
| 19 |
it did |
| 20 |
for long tim ago. There are historical (or some other) reasons for making |
| 21 |
VI default |
| 22 |
editor for this utility. It's like they don't respect not only endusers |
| 23 |
favours but |
| 24 |
the developers' too, no? |
| 25 |
|
| 26 |
WHY NOT CHECK if vim binary is in place and ONLY THEN (when it's obviously |
| 27 |
absent) |
| 28 |
hardcode the Gentoo Best Award of Choice Editor? |
| 29 |
|
| 30 |
I repeat once more. |
| 31 |
Every user who has VIM installed on theirs systems is forced to do extra |
| 32 |
configuration, to make sudo work as expected, just because someone prefer |
| 33 |
other editor and thinks that vanilla choice is bad. Isn't that just stupid? |
| 34 |
|
| 35 |
-- |
| 36 |
Best regards, Spinal |
Archives