1 |
On Tue, 2003-04-29 at 05:32, Aron Griffis wrote: |
2 |
> Hi Björn, |
3 |
> |
4 |
> Björn Lindström wrote: [Mon Apr 28 2003, 09:16:44PM EDT] |
5 |
> > This is really ugly. The expected behaviour would doubtlessly be that |
6 |
> > USE=X means that vim will have X support. |
7 |
> > |
8 |
> > Wouldn't using X combined with a suitable ewarning be better? |
9 |
> |
10 |
> Unfortunately I think you are wrong. Most users that I have encountered |
11 |
> do not expect "emerge vim" to pull in xfree, even when USE=X. This is a |
12 |
> very frequently asked question on IRC and in the mailing lists. |
13 |
> |
14 |
|
15 |
This thread got way too long, so I will skip it ... say if this was |
16 |
suggested before. |
17 |
|
18 |
Lets see if we got this right: |
19 |
|
20 |
We do not want vim to pull in X, but in some cases we still want it |
21 |
to be able to use X (not gvim, but vim with X hooks). |
22 |
|
23 |
What about for normal vim: |
24 |
|
25 |
1) Do not take heed of the 'X' use flag, except then it is '-X', |
26 |
or [ -z "`use X`" ], and then disabled it totally. |
27 |
|
28 |
2) Do not DEPEND on X under any circumstances. |
29 |
|
30 |
3) Do however build X support if we detect X ... meaning, do not |
31 |
add a --with-x or --without-x (or whatever), except for 1). |
32 |
|
33 |
We then will have vim that do not pull in X, but if you really want |
34 |
X support, you just go: |
35 |
|
36 |
# emerge xfree vim |
37 |
|
38 |
if X is not already installed. |
39 |
|
40 |
|
41 |
|
42 |
-- |
43 |
|
44 |
Martin Schlemmer |
45 |
Gentoo Linux Developer, Desktop/System Team Developer |
46 |
Cape Town, South Africa |