public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dennis Schridde <devurandom@gmx.net>
To: gentoo-dev@lists.gentoo.org
Cc: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
Subject: Re: [gentoo-dev] Addressing split usage of USE=gles[123]
Date: Thu, 21 Nov 2019 08:24:01 +0100	[thread overview]
Message-ID: <4717153.sRdt6XMvZm@monk> (raw)
In-Reply-To: <20191121033234.GE8235@cloudsdale.the-delta.net.eu.org>

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Hello everyone!

On Donnerstag, 21. November 2019 04:32:34 CET Haelwenn (lanodan) Monnier
wrote:
> I noticed for some time that there seems to be two use cases for the
> gles[123] family of USE flags in gentoo repo:
> 1. enabling support of OpenGL ES, which seems interesting to have for
> more runtime choices, probably better usage of the drivers and better
> binary-compat support.
> 2. switching from OpenGL (so the full API) to Open GL ES (reduced API),
> which is an entirely different kind of action as that reduces it quite
> significantly but might be useful for machines where the drivers do not
> provide (good) OpenGL.

I just recently ran into this, putting USE=gles2 in make.conf, thinking that
only the first kind of flags existed.  Thus I second this proposal.

We could start bikeshedding about the naming (e.g. 1. gles2, 2. only-gles2, to
keep it shorter), but I don't think that will lead us anywhere and will just
delay the execution of this plan.

Thanks for proposing this!
--Dennis

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2019-11-21  8:07 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 [this message]
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
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=4717153.sRdt6XMvZm@monk \
    --to=devurandom@gmx.net \
    --cc=contact@hacktivis.me \
    --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