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