| 1 |
On 04/30/2017 06:36 AM, Mart Raudsepp wrote: |
| 2 |
> Ühel kenal päeval, L, 29.04.2017 kell 22:32, kirjutas Walter Dnes: |
| 3 |
>> Is it considered a reportable bug? |
| 4 |
>> |
| 5 |
>> [i660][waltdnes][~] grep :graphite /usr/portage/profiles/*.desc |
| 6 |
>> /usr/portage/profiles/use.local.desc:dev-lang/gnat-gpl:graphite - Add |
| 7 |
>> support for the framework for loop optimizations based on a |
| 8 |
>> polyhedral intermediate representation |
| 9 |
>> /usr/portage/profiles/use.local.desc:media-libs/harfbuzz:graphite - |
| 10 |
>> Use graphite to render complex non-Roman writing systems |
| 11 |
>> /usr/portage/profiles/use.local.desc:sys-devel/gcc:graphite - Add |
| 12 |
>> support for the framework for loop optimizations based on a |
| 13 |
>> polyhedral intermediate representation |
| 14 |
>> |
| 15 |
>> The "graphite" USE flag means something entirely different for |
| 16 |
>> harfbuzz, i.e. build media-libs/harfbuzz against media-gfx/graphite2 |
| 17 |
> |
| 18 |
> That's why they are local. You aren't supposed to go and enable those |
| 19 |
> flags globally usually. |
| 20 |
|
| 21 |
This statement is a big confusion for users and is a pet peeve of mine. |
| 22 |
|
| 23 |
There is no such thing as calling a USE flag "local" or "global" except |
| 24 |
for where the description lies. |
| 25 |
|
| 26 |
If they want to enable a flag to apply system-wide, then it does not |
| 27 |
matter where the description is. To users, a USE flag is a USE flag. |
| 28 |
|
| 29 |
Brian |
Archives