Gentoo Archives: gentoo-dev

From: Matt Turner <mattst88@g.o>
To: gentoo development <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Addressing split usage of USE=gles[123]
Date: Thu, 21 Nov 2019 19:26:46
Message-Id: CAEdQ38Hd=1X_kN2mgZhBxDCrvsS=AHTOHTmpZFA6V8oSWOOY1w@mail.gmail.com
In Reply to: [gentoo-dev] Addressing split usage of USE=gles[123] by "Haelwenn (lanodan) Monnier"
1 On Wed, Nov 20, 2019 at 10:32 PM Haelwenn (lanodan) Monnier
2 <contact@×××××××××.me> wrote:
3 >
4 > Hello gentoo-dev,
5 >
6 > First proposition on this list so hopefully not missing some kind of
7 > netiquette/policy.
8 >
9 > I noticed for some time that there seems to be two use cases for the
10 > gles[123] family of USE flags in gentoo repo:
11 > 1. enabling support of OpenGL ES, which seems interesting to have for
12 > more runtime choices, probably better usage of the drivers and better
13 > binary-compat support.
14 > 2. switching from OpenGL (so the full API) to Open GL ES (reduced API),
15 > which is an entirely different kind of action as that reduces it quite
16 > significantly but might be useful for machines where the drivers do not
17 > provide (good) OpenGL.
18 >
19 > To reflect this I think the "gles[123]" USE flags should be renamed,
20 > first kind to "gles[123]support" and second kind to "gles[123]only".
21 > Might also be the time to globalize them? I'm not sure but I think that
22 > would help in signalling which USE flags are to be used in packages.
23 > (and I'm probably not the only one which tends to only put global USE
24 > flags in make.conf, this kind of USE flags being the reason)
25
26 I think this is a good idea. I would suggest gles[123] and
27 gles[123]-only to avoid some of the churn. Changing gles[123] to
28 gles[123]-support would mean changing a ton of reverse dependencies of
29 Mesa, and I think that's a bad idea.
30
31 > ## Second kind, switch from OpenGL to OpenGL ES (20 packages)
32 > dev-libs/weston:gles2 - Use GLESv2 cairo instead of full GL
33 > dev-python/PyQt5:gles2 - Use GLES 2.0 or later instead of full OpenGL
34 > dev-qt/qt3d:gles2 - Use GLES 2.0 or later instead of full OpenGL
35 > dev-qt/qtdatavis3d:gles2 - Use GLES 2.0 or later instead of full OpenGL
36 > dev-qt/qtdeclarative:gles2 - Use GLES 2.0 or later instead of full OpenGL
37 > dev-qt/qtgui:gles2 - Use GLES 2.0 or later instead of full OpenGL
38 > dev-qt/qtmultimedia:gles2 - Use GLES 2.0 or later instead of full OpenGL
39 > dev-qt/qtopengl:gles2 - Use GLES 2.0 or later instead of full OpenGL
40 > dev-qt/qtprintsupport:gles2 - Use GLES 2.0 or later instead of full OpenGL
41 > dev-qt/qtwebkit:gles2 - Use GLES 2.0 or later instead of full OpenGL
42 > dev-qt/qtwidgets:gles2 - Use GLES 2.0 or later instead of full OpenGL
43 > games-emulation/mupen64plus-core:gles2 - Use GLES2 instead of OpenGL
44 > games-emulation/mupen64plus-video-glide64mk2:gles2 - Use GLES2 instead of OpenGL
45 > games-emulation/mupen64plus-video-rice:gles2 - Use GLES2 instead of OpenGL
46 > kde-apps/kdenlive:gles2 - Use GLES 2.0 or later instead of full OpenGL
47 > kde-frameworks/plasma:gles2 - Use GLES 2.0 or later instead of full OpenGL
48 > kde-plasma/kwin:gles2 - Use OpenGL ES 2 instead of full GL
49 > sci-libs/opencascade:gles2 - Use OpenGL ES 2.0
50 > www-plugins/freshplayerplugin:gles2 - Use system GLESv2 libraries instead of ANGLE for shader translation
51 > www-plugins/lightspark:gles - Replace default OpenGL renderer with GLESv2
52
53 Making a pull request to change these seems like a great plan. I'll be
54 happy to help or review.