On Fri, Oct 02, 2009 at 12:09:23PM +0200, Jes??s Guerrero wrote: > On Fri, 2 Oct 2009 04:54:42 -0500, forgottenwizard > <[email protected]> wrote: > > How about a custom_editor flag, as you suggested, then an EDITOR > > variable in make.conf? Thats the only way I could see being able to > > solve this problem without invariably screwing someone. This would > > provide a fairly sane default while giving the user the choice to use > > something else. > > That would be the only way that it would make sense to me. Just like we > have VIDEO_CARDS, some GENTOO_EDITOR variable would be nice for this. But > ebuilds and eclasses would need to be aware of this to push the correct > dependencies. It's not that trivial to addapt portage to a new portage > variable. The USE flag idea is non-viable and doesn't make sense. > > It really isn't a big deal to configure yourself anyways. So unless some > developer is interested in this, I doubt they are going to do the job > unless some pristine and already working patch is sent to them, and someone > is willing to work on a collaborative way, and not just throwing > <the-editor-I-preffer> blindingly in the sudo ebuild. > > -- > Jes??s Guerrero >
Set an EDITOR var in make.conf, then set a USE-flag for sudo to honor this setting. If you set EDITOR to a valid atom (app-admin/vim, for example), then you may be able to use that as a direct dependency, or have the ebuild spit out a warning that $EDITOR isn't installed if that is the case. I'm not suggesting a USE-flag for everything, but more as a simple switch that tells the ebuild to use the users settings instead of the distro default.
