1 |
Alexis Ballier schrieb: |
2 |
> On Sun, 11 Nov 2012 11:41:05 +0100 |
3 |
> Thomas Sachau <tommy@g.o> wrote: |
4 |
> |
5 |
>> If there are no objections, i plan to add E_MODULES and E_MODULES_CONF |
6 |
>> to the list of USE_EXPAND variables for x11-wm/enlightenment:0.17, in |
7 |
>> the next days. |
8 |
>> |
9 |
> |
10 |
> i doubt there will be any objection but with such information there |
11 |
> cant be any :) |
12 |
|
13 |
You destroyed my plan ;-) |
14 |
> |
15 |
> - there is no x11-wm/enlightenment:0.17 in the tree |
16 |
|
17 |
This is currently in the enlightenment overlay. Since there are now |
18 |
alpha snapshots, i plan to add it to the main tree after doing some |
19 |
tests in the overlay (including the usage of the USE_EXPAND variable). |
20 |
|
21 |
> - what will be the possible values and use case of these variables ? |
22 |
|
23 |
e17 has a good amount of modules, which can be excluded at compile time. |
24 |
Each module has a USE flag, some examples for those USE flags: |
25 |
|
26 |
e_modules_conf-theme, e_modules_conf-wallpaper2, e_modules_ibar, |
27 |
e_modules_temperature |
28 |
|
29 |
> - considering gentoo generally uses e-prefixed names (econf, emake, |
30 |
> etc.) maybe its wiser to name the variables E17_* instead of only |
31 |
> E_*, or ENLIGHTENMENT_*, so that it makes the "confusion" harder. |
32 |
> |
33 |
|
34 |
Those functions are internal ebuild functions, while the USE_EXPANDed |
35 |
var is exposed to and may be used by the user, so i dont see a high risk |
36 |
of people mixing them. Maybe some other people can also comment on this? |
37 |
|
38 |
|
39 |
-- |
40 |
|
41 |
Thomas Sachau |
42 |
Gentoo Linux Developer |