From: Michael 'veremitz' Everitt <gentoo@veremit.xyz>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Addressing split usage of USE=gles[123]
Date: Thu, 21 Nov 2019 22:05:44 +0000 [thread overview]
Message-ID: <4c0f02d9-8792-f752-25c8-bb3c8a9e5d1e@veremit.xyz> (raw)
In-Reply-To: <3510669.sfXIqWOT4O@ernie>
[-- Attachment #1.1: Type: text/plain, Size: 1361 bytes --]
On 21/11/19 21:53, Dennis Schridde wrote:
> On Donnerstag, 21. November 2019 09:11:46 CET Mart Raudsepp wrote:
>> See also this related old thread:
>> https://archives.gentoo.org/gentoo-dev/message/e04f6d321e424a237af62721d1d09
>> 211
> I think tackling the triad of opengl/gles, egl/glx, X/wayland is also a good
> idea. Generally, all these probably have to distinguish between "support for
> XYZ" and "use only XYZ", the latter hopefully being the exception, so that the
> former can take the shorter use-flag. That's what I don't like about the
> proposal from 2018: Globally enabling USE=gles will have different effects on
> different packages. That's also what I like about the recent proposal: The
> flags are more explicit.
>
> --Dennis
I don't think the problem is so much in the principle of making a change,
or even the specifics of any particular permutation of change, it's who
gets to manage and implement the change in a maintainable fashion, and who
has to deal with the fallout of any changes occurring where a particular
scenario 'slips through the net'....
If you can convince the latter people that there is no problem arising from
making said changes, and you ensure that there genuinely *is* minimal
impact (by whatever means) then you stand a much better chance of this
change actually being implemented ..
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2019-11-21 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 3:32 [gentoo-dev] Addressing split usage of USE=gles[123] Haelwenn (lanodan) Monnier
2019-11-21 7:24 ` Dennis Schridde
2019-11-21 8:11 ` Mart Raudsepp
2019-11-21 21:53 ` Dennis Schridde
2019-11-21 22:05 ` Michael 'veremitz' Everitt [this message]
2019-11-21 22:09 ` Matt Turner
2019-11-24 17:30 ` Matt Turner
2019-11-21 16:45 ` Michael Orlitzky
2019-11-21 19:26 ` Matt Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c0f02d9-8792-f752-25c8-bb3c8a9e5d1e@veremit.xyz \
--to=gentoo@veremit.xyz \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox