From: Matt Turner <mattst88@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Cc: Mart Raudsepp <leio@gentoo.org>
Subject: Re: [gentoo-dev] Addressing split usage of USE=gles[123]
Date: Thu, 21 Nov 2019 17:09:38 -0500 [thread overview]
Message-ID: <CAEdQ38HPjmY2JoruRk5NyUL782--LvRvOXN-jvKoU8d3t-9xZA@mail.gmail.com> (raw)
In-Reply-To: <3510669.sfXIqWOT4O@ernie>
On Thu, Nov 21, 2019 at 4:54 PM Dennis Schridde <devurandom@gmx.net> 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.
Totally agree. FWIW, we have bugs filed about this for USE=wayland [0]
and USE=USE={egl,gles{,1,2,3}}.
I would be happy to see someone take up this project. I'll be happy to help.
[0] https://bugs.gentoo.org/627714
[1] https://bugs.gentoo.org/627758
next prev parent reply other threads:[~2019-11-21 22:09 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
2019-11-21 22:09 ` Matt Turner [this message]
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=CAEdQ38HPjmY2JoruRk5NyUL782--LvRvOXN-jvKoU8d3t-9xZA@mail.gmail.com \
--to=mattst88@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=leio@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