1 |
Doug Goldstein wrote: |
2 |
> While the rule of thumb has been if an eclass needs something it should |
3 |
> provide it's own depends. However the virtualx eclass needs to be |
4 |
> different simply because in some cases it's only uses for tests (this is |
5 |
> it's most common usage in the whole) tree. When it's used for tests |
6 |
> pulling in the xorg-server the most ideal situation would be if |
7 |
> xorg-server was only pulled in on USE=test because currently for anyone |
8 |
> emerging an app that uses GTK+ they have a weird situation in the fact |
9 |
> that all of GTK+'s depends that have USE=X use it to mean libX11 (as do |
10 |
> most usages of the X USE flag), however GTK+ itself due to it's usage of |
11 |
> the virtualx eclass pulls in xorg-server when USE=X, which is only used |
12 |
> for tests. This results in a confusing experience for users looking to |
13 |
> built a headless machine. |
14 |
> |
15 |
> It'd be a lot more consistent if ebuilds provided a USE flag or directly |
16 |
> depended on the xorg-server and then used the functions in the eclass. |
17 |
> So in summary, those are the changes I plan on making very shortly. If |
18 |
> someone's got some input, please speak up. |
19 |
> |
20 |
> |
21 |
Alright... after talking to Diego, Dave, and Remi the final result that |
22 |
I've come up with is the following: |
23 |
|
24 |
VIRTUALX_CONDITIONAL_USE="test" |
25 |
|
26 |
inherit virtualx |
27 |
|
28 |
That'll result in virtualx adding the following: |
29 |
|
30 |
DEPEND="test? ( x11-base/xorg-server x11-apps/xhost )" |
31 |
|
32 |
if VIRTUALX_CONDITIONAL_USE is unset (as it will be for all ebuilds |
33 |
initially) the default will be "X". Which means the default is the same |
34 |
as what we've got today. If it's set to an empty string, it'll always be |
35 |
required. Otherwise, it will use the supplied USE flag. |
36 |
|
37 |
-- |
38 |
Doug Goldstein |