public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 7/8] profiles/use.desc: Make USE=egl global
Date: Tue, 19 Dec 2023 22:23:45 +0200	[thread overview]
Message-ID: <e20c1869834e401d7ab364f51c5415107f3d6ca3.camel@gentoo.org> (raw)
In-Reply-To: <c2618ffb39b8cb52dcb2b4ddaae3859738ea61ec.camel@gentoo.org>

On Tue, 2023-12-19 at 12:50 +0100, Michał Górny wrote:
> > > --- a/media-plugins/gst-plugins-gtk/metadata.xml
> > > +++ b/media-plugins/gst-plugins-gtk/metadata.xml
> > > @@ -6,7 +6,6 @@
> > >         <name>GStreamer package maintainers</name>
> > >  </maintainer>
> > >  <use>
> > > -       <flag name="egl">Enable EGL platform usage</flag>
> > >         <flag name="gles2">Enable gtkglsink OpenGL sink based on
> > > GLESv2 API</flag>
> > >         <flag name="opengl">Enable gtkglsink OpenGL sink based on
> > > desktop OpenGL API</flag>
> > >  </use>
> > 
> > Please do not lose extra information provided in local descriptions
> > in this and many other cases where you remove the local description
> > (in other proposed global USE flag cases as well). Just don't
> > remove the local description then. Thanks.
> > 
> 
> I've used my best judgment to figure out whether the local
> description actually provides any "extra information".  I didn't
> touch the gtkglsink-related flags since they provided some
> information. I fail to see how "platform usage" adds any information.

With the tabs in the raw patch indent rendered as 8 spaces, my eyes
shifted (no less than on 3 looking occurrences while also trying to get
only this chunk into the reply) and I thought you are removing
precisely that gtkglsink comment, sorry!

> If you have "other proposed global USE flag cases" that are removing
> information, please be more specific.

I don't think any of these are very important, but if I were to
nitpick:

* x11-apps/mesa-progs local gles2 USE desc looked vaguely more useful
than the new global; might be even more useful if it named the
utilities by name (main one of interest is es2_info).
* "asm - Enable using assembly for optimization" reads a bit weird -
ultimately C, rust, etc end up using assembly in a way too. I would
have went with something more of the "Enable use of hand optimized
assembly routines" theme for the global desc.
* gnustep-base/gnustep-gui USE=speech seems to have told something
completely different than the global USE flag; maybe was looked into
and determined it's actually indeed text-to-speech* Some specify what
dep is used, but in many cases it's the obvious candidate. Maybe games-
engine/scummvm isn't that obvious. But users will see from the deptree.
* kde-apps/konqueror and net-misc/eventd specifies USE=speech installs
a plugin, which might be useful information IF that's something that
might need to be enabled by user on top to load the plugin. Not
important.


Mart


  reply	other threads:[~2023-12-19 20:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17 16:05 [gentoo-dev] [PATCH 0/8] A batch of global USE flags Michał Górny
2023-12-17 16:05 ` [gentoo-dev] [PATCH 1/8] profiles/use.desc: Add USE=speech as a global USE flag Michał Górny
2023-12-17 16:05 ` [gentoo-dev] [PATCH 2/8] profiles/use.desc: Add USE=sid " Michał Górny
2023-12-17 16:05 ` [gentoo-dev] [PATCH 3/8] profiles/use.desc: Make USE={otf,ttf} global Michał Górny
2023-12-17 16:05 ` [gentoo-dev] [PATCH 4/8] profiles/use.desc: Make USE=opencl global Michał Górny
2023-12-17 16:05 ` [gentoo-dev] [PATCH 5/8] profiles/use.desc: Make USE=lto global Michał Górny
2023-12-17 16:05 ` [gentoo-dev] [PATCH 6/8] profiles/use.desc: Make USE=gles2 global Michał Górny
2023-12-17 16:05 ` [gentoo-dev] [PATCH 7/8] profiles/use.desc: Make USE=egl global Michał Górny
2023-12-19  8:33   ` Mart Raudsepp
2023-12-19 11:50     ` Michał Górny
2023-12-19 20:23       ` Mart Raudsepp [this message]
2023-12-17 16:05 ` [gentoo-dev] [PATCH 8/8] profiles/use.desc: Make USE=asm global Michał Górny

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=e20c1869834e401d7ab364f51c5415107f3d6ca3.camel@gentoo.org \
    --to=leio@gentoo.org \
    --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