From: Filip Kobierski <fkobi@pm.me>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] [RFC] New global USE flag -- twolame
Date: Thu, 05 Dec 2024 21:04:18 +0000 [thread overview]
Message-ID: <OVRP1CTlp6Cg4Mjwks9XYS459pub34W-FRQHcEDey9mu2jV93G5fSiy3Vlxiw7XEJ1BpN-AP4wzocifwgCWAWdzTXNA6v7ZF4YdP4x81ONQ=@pm.me> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 683 bytes --]
Hello,
lately I have noticed that audacity can use twolame.
I have researched that flag and noticed that all 9 packages
listing it as a USE flag use media-sound/twolame.
I suggest adding twolame as a global USE flag with a description
used by media-libs/avidemux-plugins:
"Enable TwoLAME support via media-sound/twolame, an optimised MPEG Audio Layer 2 (MP2) encoder."
I think it fits all the software uses perfectly, besides FFMPEG,
which right now points out that it is an alternative to an
internal encoder.
I think it only makes sense to have it be a global USE flag since
many packages use it.
What do you think about it?
~~~~
Kind regards
Filip Kobierski
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
reply other threads:[~2024-12-05 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='OVRP1CTlp6Cg4Mjwks9XYS459pub34W-FRQHcEDey9mu2jV93G5fSiy3Vlxiw7XEJ1BpN-AP4wzocifwgCWAWdzTXNA6v7ZF4YdP4x81ONQ=@pm.me' \
--to=fkobi@pm.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