Ah, so this happens when no package provides $(which vi)? Then weshould default to something that is universally available.
Check fcron configure.in. Configure get editor from enviroment parameter EDITOR it not set by default vi.
--with-editor=/bin/nano would do fine. I already CC'd bsd@ on the bu
On Monday 13 November 2006 20:21, Jeroen Roovers wrote:
> --with-editor=/bin/nano would do fine. I already CC'd bsd@ on the bug
> to figure out if nano is part of their defaults, but it probably does
> not matter because BSD does have $(which vi) AFAIK.
We are Gentoo in that regard, we don't instal
On Mon, 13 Nov 2006 11:17:37 +0500
"Anatoly Shipitsin" <[EMAIL PROTECTED]> wrote:
> Okey. I'm remove all get editor from runtime enviroment EDITOR and
> disable --with-editor. The run emerge fcron. I'm got:
>
> checking for vi... no
> configure: error:
> Cannot determine path to vi: try option --
You mean I ought to go read the bug I referred to a few times in themessage you are responding to? I did. In fact, I wrote a lot of the
comments there. I am CC'd on that bug. I even recorded the originalcomplaint on that bug stating that the ebuild should not rely on theenvironment to find a value
On Sunday 12 November 2006 06:29, Peter Volkov (pva) wrote:
> On Sun, 2006-11-12 at 05:54 -0500, Mike Frysinger wrote:
> > in the example usages you cited, people where using `sudo` to just
> > avoid running `su -` first ... in other words, their sudo was
> > unlimited ... updating the sudoers file
On Mon, 13 Nov 2006 09:20:09 +0500
"Anatoly Shipitsin" <[EMAIL PROTECTED]> wrote:
> Without --with-editor fcrom configure get editor from enviroment
> parameter EDITOR.
> This is wrong see bug 149376.
You mean I ought to go read the bug I referred to a few times in the
message you are respondin
No, it's not needed for fcron at all, and I already explained why in[1]. Progressing through [2-4] I thought the fcron issue might have
been fixed, but the virtual/editor discussion had started by then and Idecided I had nothing more to add. Again: fcron builds and works finewithout at all setting
On Sun, 12 Nov 2006 21:57:07 +0500
"Anatoly Shipitsin" <[EMAIL PROTECTED]> wrote:
> >
> > Although I do think you're making a big fuss over a tiny cosmetic
> > issue.
> >
> > This changes need not for sudo. It's need for fcron. And probaly
> > any
> package use define editor on configuration sta
Although I do think you're making a big fuss over a tiny cosmeticissue.
This changes need not for sudo. It's need for fcron. And probaly any package use define editor on configuration stage.
On Sun, Nov 12, 2006 at 08:59:03PM +0500, Anatoly Shipitsin wrote:
> >> Use abstract depend provide by same packages and set hardcoded depend
> >> provided by one package (nano) is right?
> >
> >No, is not right.
> >
> But why it's not need change? I'm talk not only sudo.
I dont know about the oth
"Doctor, it hurts when I do this"very funny :)
It isnt hardcoded, it's configurable.If this not hardcoded. I'm think use this at new fcron ebuild. This really close problem bug #149376 ;)
No, you set the correct editor, I dont know which one you use.
I'm told about ebuild. I'm can use virtual/edit
> Use abstract depend provide by same packages and set hardcoded depend
> provided by one package (nano) is right?No, is not right.But why it's not need change? I'm talk not only sudo.
On Sun, Nov 12, 2006 at 08:17:18PM +0500, Anatoly Shipitsin wrote:
> >
> >Talking specifically about sudo, I think you're making a big deal out of
> >a very minor thing, primarily because I cannot think of a sane example
> >of when $EDITOR and $VISUAL are not set and visudo (which requires an
> >in
On Sun, Nov 12, 2006 at 08:38:52PM +0500, Anatoly Shipitsin wrote:
> >I'm think if we set hardcoded editor nano at configure in sudo,ebuild its
> >> should DEPEND at nano editor not virtual/editor.
> >
> >Then you would be wrong.
> >
>
> Use abstract depend provide by same packages and set hardcod
> Check sudo-1.6.8_p9-r2.ebuild> In DEPEND we see virtual/editor but
> in configure> --with-editor=/bin/nano>> But virtual/editor can provide by vi nano & etc editor. You think its right?> DEPEND set virtual/editor but configure use nano as hardcoded editor.
Yes, I think it's right. That option doe
On Sun, Nov 12, 2006 at 06:21:56PM +0500, Anatoly Shipitsin wrote:
> >This question is nonsensical. I guess you dont understand what sudo
> >does, it's too complicated to explain here, you should consult the
> >documentation.
>
> I'm told about emerge package not runtime. May you don't understand
Talking specifically about sudo, I think you're making a big deal out ofa very minor thing, primarily because I cannot think of a sane example
of when $EDITOR and $VISUAL are not set and visudo (which requires aninteractive editor) would be invoked.It's problem exist for any package use configure f
On Sun, Nov 12, 2006 at 04:21:21PM +0300, Peter Volkov (pva) wrote:
> On Sun, 2006-11-12 at 12:15 +, Tavis Ormandy wrote:
> > The only `hardcoded` editor is the fallback editor for
> > visudo
>
> And this is the problem I'm talking about. I do not see any reasons to
> keep this not working fal
This question is nonsensical. I guess you dont understand what sudodoes, it's too complicated to explain here, you should consult the
documentation.I'm told about emerge package not runtime. May you don't understand me.Check sudo-1.6.8_p9-r2.ebuildIn DEPEND we see virtual/editor butin configure --w
On Sun, 2006-11-12 at 12:15 +, Tavis Ormandy wrote:
> The only `hardcoded` editor is the fallback editor for
> visudo
And this is the problem I'm talking about. I do not see any reasons to
keep this not working fallback. There are parts of code that just do not
work in Gentoo.
> which can be
On Sun, Nov 12, 2006 at 04:30:48PM +0500, Anatoly Shipitsin wrote:
> >You can set `Defaults env_keep=EDITOR` in your sudoers file if you want,
> >or what I do is `Defaults:%wheel !env_reset`, to allow users in group
> >wheel to use sudo without the environment being scrubbed.
> >
>
> Ok. How you p
On Sun, Nov 12, 2006 at 02:32:56PM +0300, Peter Volkov (pva) wrote:
> On Sun, 2006-11-12 at 11:06 +, Tavis Ormandy wrote:
> > You can set `Defaults env_keep=EDITOR` in your sudoers file if you
> > want, or what I do is `Defaults:%wheel !env_reset`, to allow users in
> > group wheel to use sudo
Peter Volkov (pva) wrote:
> Or... what do you mean by that:
> "the sudo file has the ability to specify editor's, so why not tell
> people to change their sudo config file ?"
>
> English is not my native language thus may be I just misunderstood your
> idea here. Sorry.
...that the people should
On Sun, 2006-11-12 at 11:06 +, Tavis Ormandy wrote:
> You can set `Defaults env_keep=EDITOR` in your sudoers file if you
> want, or what I do is `Defaults:%wheel !env_reset`, to allow users in
> group wheel to use sudo without the environment being scrubbed.
Of course I know about that. And I
On Sun, 2006-11-12 at 05:54 -0500, Mike Frysinger wrote:
> in the example usages you cited, people where using `sudo` to just
> avoid running `su -` first ... in other words, their sudo was
> unlimited ... updating the sudoers file to allow EDITOR via env_keep
> would work fine for them
>
> in tha
On Sun, Nov 12, 2006 at 12:27:12PM +0300, Peter Volkov (pva) wrote:
> work[3,4] (yes... if EDITOR is not set). But EDITOR *is not* set when
> program is started from sudo because sudo for security reasons drops
> environment (are there any other cases when environment is dropped?).
You can set `De
On 11/12/06, Peter Volkov (pva) <[EMAIL PROTECTED]> wrote:
And does not prevents sudo from
removing EDITOR from environment.
in the example usages you cited, people where using `sudo` to just
avoid running `su -` first ... in other words, their sudo was
unlimited ... updating the sudoers file t
then we end up with having to maintain a list of "safe" EDITORs anddealing with people who want to edit their own favorite editor
the sudo file has the ability to specify editor's, so why not tellpeople to change their sudo config file ?It's not automatic.Other way is remove virtual/editor. And set
On Sun, 2006-11-12 at 05:26 -0500, Mike Frysinger wrote:
> then we end up with having to maintain a list of "safe" EDITORs and
> dealing with people who want to edit their own favorite editor
>
> the sudo file has the ability to specify editor's, so why not tell
> people to change their sudo confi
On 11/12/06, Thilo Bangert <[EMAIL PROTECTED]> wrote:
is there a list of sudo 'safe' EDITORs somewhere?
then we end up with having to maintain a list of "safe" EDITORs and
dealing with people who want to edit their own favorite editor
the sudo file has the ability to specify editor's, so why n
On 2006-11-12 at 04:34 -0500, Mike Frysinger wrote:
> why not modify sudo to not filter the EDITOR env var then there is no
> more problem
Considering that this is the only situation where environment is
dropped... yes this fixes sudo problem. The other possible solution is:
#!/bin/bash
export ED
On Sun, Nov 12, 2006 at 04:56:33AM -0500, Mike Frysinger wrote:
> On 11/12/06, Harald van Dijk <[EMAIL PROTECTED]> wrote:
> >On Sun, Nov 12, 2006 at 04:34:25AM -0500, Mike Frysinger wrote:
> >> On 11/12/06, Peter Volkov (pva) <[EMAIL PROTECTED]> wrote:
> >> >The possible solution is to add virtual/e
> why not modify sudo to not filter the EDITOR env var then there is no
> more problem
no, there is a very valid reason why sudo filters the EDITOR env var.
sudo should probably be fixed to (re)set the EDITOR variable to a 'safe'
systemwide default, instead of stripping it completely.
is there
On 11/12/06, Harald van Dijk <[EMAIL PROTECTED]> wrote:
On Sun, Nov 12, 2006 at 04:34:25AM -0500, Mike Frysinger wrote:
> On 11/12/06, Peter Volkov (pva) <[EMAIL PROTECTED]> wrote:
> >The possible solution is to add virtual/editor ebuild
>
> this is a horrible idea
>
> why not modify sudo to not f
On Sun, Nov 12, 2006 at 04:34:25AM -0500, Mike Frysinger wrote:
> On 11/12/06, Peter Volkov (pva) <[EMAIL PROTECTED]> wrote:
> >The possible solution is to add virtual/editor ebuild
>
> this is a horrible idea
>
> why not modify sudo to not filter the EDITOR env var then there is no
> more proble
On 11/12/06, Peter Volkov (pva) <[EMAIL PROTECTED]> wrote:
The possible solution is to add virtual/editor ebuild
this is a horrible idea
why not modify sudo to not filter the EDITOR env var then there is no
more problem
-mike
--
gentoo-dev@gentoo.org mailing list
Hello.
Anatoly raised really important concern and currently I've started to
think about fix. One possible solution requires virtual/editor to suite
glep 37 and thus affects many packages. So... wondering why this change
was not done I'd like to discuss the problem on the list.
Problem:
There are
37 matches
Mail list logo
