Welcome to Gentoo Forums, the mailing-list alternative.
https://forums.gentoo.org/
You reopened it twenty minutes after flameeyes' "And I start to get quite pissed off by your insisting reopening this bug." comment.Spinal_by wrote:I didn't reopen it after it was asked.Earthwings wrote:The bug reporter kept reopening the bug although being asked not to.Hu wrote:For that matter, why is the bug now restricted?
Leave the bug open.vasily_pupkin wrote:What should maintainer do?
This options or BUILDING, not for configuration. visudo have some resrictions with configuratio-when-building, This configuration setted up to stage-default. All okbrezblock wrote: USE="-nano -emacs vim"
This is true *gentoo way* Is in't it?
Spinal_by wrote:gentoo is all about 'the user sets the stuff as he wants it' and you are complaining that you have to set something?vasily_pupkin wrote:I prefer when package maintainer spend 5 minute ONCE to do things work as expected, thanSpinal_by wrote: (By the way. I don't know anything about visudo till this morning, but i spend about 5 minutes to solve topicstarter's "problem". Is this really problem?)
when 100000 users spend 5 minute (5*100000) on doing unnecessary job.
=============================================
!!! UPDATE !!!
You can see the copy of the ticket by yourself here:
http://www.rootshell.be/~spinal/gentoo_ ... 86017.html
You know, there are distros for people like you, maybe you should have a look at ubuntu, fedora or opensuse?
what you want is to make all the non-vi users suffer because you can't be assed to set a simple one line option. Do you see the problem?
The ebuild should give the user a warning (elog/ewarn) about setting the option when they don't have nano installed. I'm sure there are some non-vi users who don't have nano.energyman76b wrote:what you want is to make all the non-vi users suffer because you can't be assed to set a simple one line option. Do you see the problem?
first time they try visudo, they get an error, they set EDITOR, everything is fine.nico-- wrote:The ebuild should give the user a warning (elog/ewarn) about setting the option when they don't have nano installed. I'm sure there are some non-vi users who don't have nano.energyman76b wrote:what you want is to make all the non-vi users suffer because you can't be assed to set a simple one line option. Do you see the problem?
Setting EDITOR does not work, that's why nano is hardcoded in the ebuild to begin with.energyman76b wrote:first time they try visudo, they get an error, they set EDITOR, everything is fine.
as several people in the very long email list thread have written, setting EDITOR works just fine.nico-- wrote:Setting EDITOR does not work, that's why nano is hardcoded in the ebuild to begin with.energyman76b wrote:first time they try visudo, they get an error, they set EDITOR, everything is fine.
RTFMnico-- wrote: Setting EDITOR does not work, that's why nano is hardcoded in the ebuild to begin with.
Which reopened the bug.Spinal_by wrote:I didn't reopen bug, I just made post, concluding what was suggested in mail-list
and attached a patch. Then I was just kicked of the ticket (I'm the ticket creator).
To reopen the bug, one should choose the option "Reopen the bug" or may leave "Resolved as CANTFIX".desultory wrote:Which reopened the bug.Spinal_by wrote:I didn't reopen bug, I just made post, concluding what was suggested in mail-list
and attached a patch. Then I was just kicked of the ticket (I'm the ticket creator).
Sorry, do you read http://www.rootshell.be/~spinal/gentoo_ ... 86017.html ?desultory wrote:Which reopened the bug.Spinal_by wrote:I didn't reopen bug, I just made post, concluding what was suggested in mail-list
and attached a patch. Then I was just kicked of the ticket (I'm the ticket creator).
jw5801 wrote:...
Anyway, I realise that this thread is not in fact about the 'bug', but more about flameeyes. So I'll say that everything I've seen of him has been positive, so this is unusual and I'm sure there was a valid reason (whether it was something you did, or otherwise), so cut him a bit of slack and don't take it to heart.
Ah look, a valid reason.http://www.rootshell.be/~spinal/gentoo_bug_report/286017.html wrote:------- Comment #4 From Diego E. 'Flameeyes' Pettenò 2009-09-24 21:39:05 0000 [reply] -------
This would require having an "editor" script and an eselect editor module, but
I really don't want to start with this myself…
------- Comment #5 From Arthur Demchenkov 2009-09-28 19:34:46 0000 [reply] -------
To Diego E. 'Flameeyes' Pettenò:
That was funny, closing that ticket as CANTFIX.
What about changing the string in ebuild:
--with-editor=/bin/nano
to something like this:
--with-editor="${EDITOR}"
Could you please forward the ticket to someone who can make decisions?
Thank you.
Normal, no, definitely typical though.brezblock wrote:Is it normal Gentoo developer's behaviour pattern?Okay. Now I'm seriously *tired* and *pissed off* and I'm going to say "bye" to
politically correctness and politeness.
If I hear one of you _again_ come up with "the Gentoo Way" *while not being a
Gentoo developer*, I'm going to ask for your bugzilla account to be locked
down.
I'm _not_ going to change this behaviour. Full stop.
Sudo wants a default (which the admin can change in the configuration file),
and that default is _the same as provided in baselayout!_ The same editor that
_is installed with the damn stages_.
You want to change it? You change it with EXTRA_ECONF.
Is it fair for *god* Gentoo developer just allow to knock off from community *mortal* users??
Is it fair to restrict community from discuss bugs and it's solution???
Um, yes it will. It pays attention to the EDITOR, I changed it on the fly and it called up whatever editor I had it set to.Spinal_by wrote:It will not make use of it without extra configuration.energyman76b wrote:why?nico-- wrote:I also ran into this issue yesterday. It would be nice if the ebuild at least printed a warning for those of us who don't have /bin/nano.
even if you don't have nano - when you set up EDITOR correctly, visudo will use whatever editor you want it to use.
According to the man page for visudo(8):energyman76b wrote:as several people in the very long email list thread have written, setting EDITOR works just fine.
and in sudo(8):There is a hard-coded list of editors that visudo will use set at compile-time that may be overridden via the editor sudoers Default variable. This list defaults to the path to vi(1) on your system, as determined by the configure script. Normally, visudo does not honor the VISUAL or EDITOR environment variables unless they contain an editor in the aforementioned editors list.
By default, the env_reset sudoers option is enabled. This causes commands to be executed with a minimal environment containing TERM, PATH, HOME, SHELL, LOGNAME, USER and USERNAME in addition to variables from the invoking process permitted by the env_check and env_keep sudoers options.
If you want to keep your environ then "sudo -E visudo" should be being used.jw5801 wrote:Ah, I see. Well, it makes sense that sudo should drop the EDITOR variable.Spinal_by wrote:jw5801 wrote:Try running "sudo visudo", that's what all this started with.Hu wrote:That's just plain incorrect. At least on my system anyway. The only place I've ever set EDITOR is in /etc/rc.conf. I rarely ever actually use sudo and haven't changed any of it's default settings, yet visudo opens emacs, not nano.
That's not entirely correct, but the problem is not related to visudo in particular, it's related to sudo. When you run `sudo <anything>' it drops most of the environment (unless you tell it not to in /etc/sudoers), otherwise you could set the EDITOR variable to whatever you wanted, then run a command that executes it and essentially run whatever you wanted to with sudo. It therefore defaults to firstly whatever environment variables are set in /etc/sudoers (which would be the simplest way to fix this problem) and secondly to whatever is hardcoded at build time.Anon-E-moose wrote:Um, yes it will. It pays attention to the EDITOR, I changed it on the fly and it called up whatever editor I had it set to.Spinal_by wrote:It will not make use of it without extra configuration.energyman76b wrote:why?nico-- wrote:I also ran into this issue yesterday. It would be nice if the ebuild at least printed a warning for those of us who don't have /bin/nano.
even if you don't have nano - when you set up EDITOR correctly, visudo will use whatever editor you want it to use.
As far as flameeyes behavior, I saw some of the "bug" discussion before it got locked and he had good reason for his attitude, IMO.
That is all that I will say on that.
Setting EDITOR does work, as I said earlier use "sudo -E visudo" or try and RTFM.nico-- wrote:Setting EDITOR does not work, that's why nano is hardcoded in the ebuild to begin with.energyman76b wrote:first time they try visudo, they get an error, they set EDITOR, everything is fine.
Yes, it is correct if you use the "-E" option with sudo. It will use your EDITOR setting, from your environment.jw5801 wrote:That's not entirely correct, but the problem is not related to visudo in particular, it's related to sudo. When you run `sudo <anything>' it drops most of the environment (unless you tell it not to in /etc/sudoers), otherwise you could set the EDITOR variable to whatever you wanted, then run a command that executes it and essentially run whatever you wanted to with sudo. It therefore defaults to firstly whatever environment variables are set in /etc/sudoers (which would be the simplest way to fix this problem) and secondly to whatever is hardcoded at build time.Anon-E-moose wrote:Um, yes it will. It pays attention to the EDITOR, I changed it on the fly and it called up whatever editor I had it set to.Spinal_by wrote:It will not make use of it without extra configuration.energyman76b wrote:why?nico-- wrote:I also ran into this issue yesterday. It would be nice if the ebuild at least printed a warning for those of us who don't have /bin/nano.
even if you don't have nano - when you set up EDITOR correctly, visudo will use whatever editor you want it to use.
As far as flameeyes behavior, I saw some of the "bug" discussion before it got locked and he had good reason for his attitude, IMO.
That is all that I will say on that.
I'm sorry for not using my time machine before posting.Anon-E-moose wrote:as I said earlier use "sudo -E visudo" or try and RTFM.
And you are giving a fine example of why flameeyes got so upset.
Code: Select all
FluidMotion naib # visudo &
[1] 31902
FluidMotion naib # ps
PID TTY TIME CMD
31891 pts/1 00:00:00 su
31894 pts/1 00:00:00 bash
31902 pts/1 00:00:00 visudo
31903 pts/1 00:00:00 vim
31904 pts/1 00:00:00 ps
[1]+ Stopped visudo
FluidMotion naib # echo $EDITOR
/usr/bin/vim
/THREADAs you can see, this file is well commented to help you set up the necessary configuration variables. You can configure your system to use unicode and define your default editor and your display manager (like gdm or kdm).
Looks like you can't read.Naib wrote:Code: Select all
FluidMotion naib # visudo & [1] 31902 FluidMotion naib # ps PID TTY TIME CMD 31891 pts/1 00:00:00 su 31894 pts/1 00:00:00 bash 31902 pts/1 00:00:00 visudo 31903 pts/1 00:00:00 vim 31904 pts/1 00:00:00 ps [1]+ Stopped visudo FluidMotion naib # echo $EDITOR /usr/bin/vim
NOTE the vim process (which is spawned by visudo) as well as the EDITOR variable is populated
Likewise the instalation handbook (section 8.c. System Information)/THREADAs you can see, this file is well commented to help you set up the necessary configuration variables. You can configure your system to use unicode and define your default editor and your display manager (like gdm or kdm).