You mean I ought to go read the bug I referred to a few times in the
message 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 original
complaint on that bug stating that the ebuild should not rely on the
environment to find a value for EDITOR. I might say I care about the
issue. :)
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 --with-editor=PATH
But i'm can't get editor from runtime. How emerge obtain right editor ?
As I recorded on that bug, fcron's build system sets it to a default
of /usr/bin/vi unless you set the --with-editor option. There's nothing
wrong with that. It just means that running crontab will fail if you do
not set EDITOR after it installs, which is what /etc/rc.conf sets to a
system-wide default.
Can i'm use solution from sudo package ?
fcron *always* uses EDITOR from the environment when running crontab, no
matter what you pass to --with-editor at configure time. Consider it a
feature.
I'm know! If this broke at configure run without this :(
Anyway, all this is already documented on the bug you mentioned. I do
not see any need to cover this ground again and again. A
simple ./configure --help should really help you find out why not
setting --with-editor fixes the problem I brought up on that bug, which
then got turned into this huge kludge (virtual/editor) to fix a
cosmetic problem, IMHO.
Remove --with-editor not fix it. For this it need set enviroment paramenter EDITOR. How resolve this problem. I'm not get any solution.
