| 1 |
>>>>> On Fri, 15 Jul 2016, waltdnes wrote: |
| 2 |
|
| 3 |
> Another day, another thread about multiple occurences of a flag in |
| 4 |
> use.local.desc. Howsabout a serious overall look at the situation? |
| 5 |
> [...] |
| 6 |
|
| 7 |
> The final result is that flagcount.txt has a count, in descending |
| 8 |
> order, of each flag in use.local.desc. It does need some manual |
| 9 |
> cleaning up, which I've done. It's file-attached. I've included |
| 10 |
> all flags with 5 or more occurences, as well as stuff that looks |
| 11 |
> like it is, or should be, a USE_expand var. The developers may want |
| 12 |
> to look at the issue of hyphens versus underscores. |
| 13 |
|
| 14 |
> pax_kernel 25 |
| 15 |
|
| 16 |
Underscores are considered reserved for USE_EXPAND, so presumably this |
| 17 |
one should be renamed. |
| 18 |
|
| 19 |
> I assume the following groups are all USE_expand variables. |
| 20 |
|
| 21 |
AFAICS, only apache2_modules_*, collectd_plugins_*, and |
| 22 |
enlightenment_modules_* are USE_EXPAND, i.e. have an entry in |
| 23 |
make.defaults of some profile. (Plus linguas_*, which is on its way |
| 24 |
out of the tree though.) |
| 25 |
|
| 26 |
> if not, then look into making it so... |
| 27 |
|
| 28 |
fbcon_frontend_*, strongswan_plugins_*, and ups_drivers_* look like |
| 29 |
candidates. Not sure about the rest. |
| 30 |
|
| 31 |
Anything that isn't a USE_EXPAND shouldn't have an underscore in its |
| 32 |
name, though ... |
| 33 |
|
| 34 |
Ulrich |
Archives