| 1 |
On Sun, 30 Apr 2017 09:48:58 -0400 |
| 2 |
Brian Evans <grknight@g.o> wrote: |
| 3 |
|
| 4 |
> If they want to enable a flag to apply system-wide, then it does not |
| 5 |
> matter where the description is. To users, a USE flag is a USE flag. |
| 6 |
|
| 7 |
Terminology wise, this is more a side effect that users are exposed to |
| 8 |
global methods of setting use flags first, and specific methods of |
| 9 |
setting use flags second. |
| 10 |
|
| 11 |
The reality is *all* USE flags have behaviour specific to the packages |
| 12 |
they're on. |
| 13 |
|
| 14 |
Just some packages share the same interpretations of the same flags, |
| 15 |
and so it *can* make sense to set them simultaneously for multiple |
| 16 |
packages. |
| 17 |
|
| 18 |
But this ends up in a "Cognition, Language, Naming things and |
| 19 |
Namespaces are hard" corner either way. |
Archives