1 |
While the rule of thumb has been if an eclass needs something it should |
2 |
provide it's own depends. However the virtualx eclass needs to be |
3 |
different simply because in some cases it's only uses for tests (this is |
4 |
it's most common usage in the whole) tree. When it's used for tests |
5 |
pulling in the xorg-server the most ideal situation would be if |
6 |
xorg-server was only pulled in on USE=test because currently for anyone |
7 |
emerging an app that uses GTK+ they have a weird situation in the fact |
8 |
that all of GTK+'s depends that have USE=X use it to mean libX11 (as do |
9 |
most usages of the X USE flag), however GTK+ itself due to it's usage of |
10 |
the virtualx eclass pulls in xorg-server when USE=X, which is only used |
11 |
for tests. This results in a confusing experience for users looking to |
12 |
built a headless machine. |
13 |
|
14 |
It'd be a lot more consistent if ebuilds provided a USE flag or directly |
15 |
depended on the xorg-server and then used the functions in the eclass. |
16 |
So in summary, those are the changes I plan on making very shortly. If |
17 |
someone's got some input, please speak up. |
18 |
|
19 |
-- |
20 |
Doug Goldstein |