| 1 |
On 1 Oct 2009, at 22:01, Volker Armin Hemmann wrote: |
| 2 |
|
| 3 |
> On Donnerstag 01 Oktober 2009, Stroller wrote: |
| 4 |
>> On 1 Oct 2009, at 21:28, Mike Edenfield wrote: |
| 5 |
>>> On 10/1/2009 3:32 PM, forgottenwizard wrote: |
| 6 |
>>>> However, I'm also wondering why the ebuild doesn't make use of the |
| 7 |
>>>> EDITOR variable as was mentioned. This defaults to nano so it |
| 8 |
>>>> should |
| 9 |
>>>> work fine in a default install, and would avoid issues like this |
| 10 |
>>>> which |
| 11 |
>>>> seems to be an arguement that the dev(s) are trying to force |
| 12 |
>>>> specific |
| 13 |
>>>> programs on the users. |
| 14 |
>>> |
| 15 |
>>> I would be hesitant to use a user-specific variable like EDITOR to |
| 16 |
>>> define the system-wide default on an ebuild. For example, what if |
| 17 |
>>> my EDITOR was set to gvim or emacs when I installed sudo, then some |
| 18 |
>>> other remote user tried to run visudo over ssh? |
| 19 |
>> |
| 20 |
>> I think it should get the $EDITOR variable set in rc.conf |
| 21 |
> |
| 22 |
> it is set in /etv/env.d - why is that not enough? |
| 23 |
|
| 24 |
Uh, because the ebuild ignores that, too, and hard-codes it. |
| 25 |
|
| 26 |
Stroller. |
Archives