Anatoly Shipitsin wrote:
Ah, so this happens when no package provides $(which vi)? Then we
should default to something that is universally available.
Check fcron configure.in <http://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 bug
to figure out if nano is part of their defaults, but it probably does
not matter because BSD does have $(which vi) AFAIK.
This solution used in sudo. But with fcron we need set DEPEND
app-editors/nano instead virtual/editor
If this is really too much trouble we could perhaps have it default to
--with-editor="$(which less)"? ;-)
it's really much trouble. Without editor fcron ebuild will broken.
So USE_EXPAND $Editor and use the flags to figure out what the default
editor should be. Or just set EDITOR so that when fcron builds it finds
the editor you used. You can always emerge fcron with EDITOR=nano and
then unmerge nano and claim fcron is 'broken'. I think most people
wouldn't care though.
The only problem currently is that EDITOR is set in /etc/profile (not
/etc/profile.env) so if you use sudo to emerge fcron, EDITOR will get
stripped from the environment, causing this problem. Then again I'd say
thats a sudo configuration problem, not necessarily a build problem.
--
gentoo-dev@gentoo.org mailing list
