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