1 |
First of all, let me thank agriffis for maintaining the vim ebuilds. |
2 |
Given the thousands (okay, only hundreds, but still) of patches |
3 |
involved, maintaining vim is quite a challenge. |
4 |
|
5 |
It seems to me that the fundamental problem is one of user education |
6 |
about the meaning of USE flags. Having people do 'USE="-X" emerge vim' |
7 |
to emerge vim without X support is principally a problem because (a) |
8 |
people don't expect that vim might depend on X, and (b) often don't know |
9 |
how to turn off X support anyway. |
10 |
|
11 |
I propose that we go ahead and have vim build with X support if people |
12 |
don't override the +X useflag, since that's most inline with Gentoo |
13 |
philosophy. At the same time, to minimize the number of bug reports I |
14 |
suggest that we also take the opportunity to discuss USE flags in the |
15 |
context of vim (and other console text editors) in the install docs. |
16 |
The install docs are the only docs that we really know almost all of our |
17 |
users actually read, so a brief primer about USE flags would be quite |
18 |
useful there, and vim is a good package to talk about since the absence |
19 |
or presence of X in USE makes a huge and obvious difference to the build |
20 |
process, which helps drive home the point about how customizable Gentoo |
21 |
is. |
22 |
|
23 |
-g2boojum- |
24 |
|
25 |
PS. I'm currently swamped grading a 5-inch stack of physical chemistry |
26 |
take-home finals, but once I get that finished I would be happy to write |
27 |
the proposed section for the install guide. |
28 |
-- |
29 |
Grant Goodyear <g2boojum@g.o> |