* [gentoo-dev] USE flag name collision in use.local.desc "graphite"
@ 2017-04-30 2:32 Walter Dnes
2017-04-30 10:36 ` Mart Raudsepp
0 siblings, 1 reply; 4+ messages in thread
From: Walter Dnes @ 2017-04-30 2:32 UTC (permalink / raw
To: Gentoo Developers
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
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] USE flag name collision in use.local.desc "graphite"
2017-04-30 2:32 [gentoo-dev] USE flag name collision in use.local.desc "graphite" Walter Dnes
@ 2017-04-30 10:36 ` Mart Raudsepp
2017-04-30 13:48 ` Brian Evans
0 siblings, 1 reply; 4+ messages in thread
From: Mart Raudsepp @ 2017-04-30 10:36 UTC (permalink / raw
To: gentoo-dev
Ü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.
That said, it does seem a bit suboptimal and maybe one of them could be
describing the feature added by the dependency instead in the USE flag
naming. So it could at least be a bug where discussions of this could
take place, even ifthat doesn't lead to changes in the end (if such a
bug didn't happen in the past)
Mart
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] USE flag name collision in use.local.desc "graphite"
2017-04-30 10:36 ` Mart Raudsepp
@ 2017-04-30 13:48 ` Brian Evans
2017-04-30 13:58 ` Kent Fredric
0 siblings, 1 reply; 4+ messages in thread
From: Brian Evans @ 2017-04-30 13:48 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1.1: Type: text/plain, Size: 1310 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] USE flag name collision in use.local.desc "graphite"
2017-04-30 13:48 ` Brian Evans
@ 2017-04-30 13:58 ` Kent Fredric
0 siblings, 0 replies; 4+ messages in thread
From: Kent Fredric @ 2017-04-30 13:58 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
On Sun, 30 Apr 2017 09:48:58 -0400
Brian Evans <grknight@gentoo.org> wrote:
> 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.
Terminology wise, this is more a side effect that users are exposed to
global methods of setting use flags first, and specific methods of
setting use flags second.
The reality is *all* USE flags have behaviour specific to the packages
they're on.
Just some packages share the same interpretations of the same flags,
and so it *can* make sense to set them simultaneously for multiple
packages.
But this ends up in a "Cognition, Language, Naming things and
Namespaces are hard" corner either way.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-04-30 13:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-04-30 2:32 [gentoo-dev] USE flag name collision in use.local.desc "graphite" Walter Dnes
2017-04-30 10:36 ` Mart Raudsepp
2017-04-30 13:48 ` Brian Evans
2017-04-30 13:58 ` Kent Fredric
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox