| 1 |
Ühel kenal päeval, L, 29.04.2017 kell 22:32, kirjutas Walter Dnes: |
| 2 |
> Is it considered a reportable bug? |
| 3 |
> |
| 4 |
> [i660][waltdnes][~] grep :graphite /usr/portage/profiles/*.desc |
| 5 |
> /usr/portage/profiles/use.local.desc:dev-lang/gnat-gpl:graphite - Add |
| 6 |
> support for the framework for loop optimizations based on a |
| 7 |
> polyhedral intermediate representation |
| 8 |
> /usr/portage/profiles/use.local.desc:media-libs/harfbuzz:graphite - |
| 9 |
> Use graphite to render complex non-Roman writing systems |
| 10 |
> /usr/portage/profiles/use.local.desc:sys-devel/gcc:graphite - Add |
| 11 |
> support for the framework for loop optimizations based on a |
| 12 |
> polyhedral intermediate representation |
| 13 |
> |
| 14 |
> The "graphite" USE flag means something entirely different for |
| 15 |
> harfbuzz, i.e. build media-libs/harfbuzz against media-gfx/graphite2 |
| 16 |
|
| 17 |
That's why they are local. You aren't supposed to go and enable those |
| 18 |
flags globally usually. |
| 19 |
That said, it does seem a bit suboptimal and maybe one of them could be |
| 20 |
describing the feature added by the dependency instead in the USE flag |
| 21 |
naming. So it could at least be a bug where discussions of this could |
| 22 |
take place, even ifthat doesn't lead to changes in the end (if such a |
| 23 |
bug didn't happen in the past) |
| 24 |
|
| 25 |
|
| 26 |
Mart |
Archives