From: Steve Dibb <beandog@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] lame use flag, local to global
Date: Wed, 10 Oct 2007 07:55:01 -0600 [thread overview]
Message-ID: <470CD9B5.3000706@gentoo.org> (raw)
In-Reply-To: <1192002003.19716.2.camel@localhost>
Mart Raudsepp wrote:
> On T, 2007-10-09 at 21:03 -0600, Steve Dibb wrote:
>> The little lame use flag has started showing up more in local use flags,
>> and all for the same purpose, MP3 support using LAME libraries. I vote
>> we move it into a global use flag. Any objections, let me know.
>>
>> $ quse -D lame
>> local:lame:media-libs/libquicktime: Support LAME mp3 encoding
>> local:lame:media-libs/mlt: Support LAME mp3 encoding
>> local:lame:media-sound/abcde: Support LAME mp3 encoding
>> local:lame:media-sound/gnusound: Enable lame support
>> local:lame:media-video/mpeg4ip: Support LAME mp3 encoding in the
>> server/mp4live
>
> Any reason to not use something like mp3enc flag instead at that point?
> mp3 USE flag is already global, and appears to mean mp3 decoding, so how
> about a general mp3 encoding USE flag? I guess merging decoding and
> encoding behind the same USE flag might be an option too.
>
Ah, I knew this question was gonna come up, should have addresed it
first time around.
The reason we have mp3 and lame use flag is because there is more than
one mp3 encoder. In almost every case of the use flag being applied
above, there is already support for another mp3 codec (ffmpeg). So,
lame adds support for lame, not for mp3, which is also provided.
When there is just one mp3 codec used in an ebuild, then it makes sense
to use just the mp3 use flag.
Steve
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-10 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 3:03 [gentoo-dev] lame use flag, local to global Steve Dibb
2007-10-10 7:40 ` Mart Raudsepp
2007-10-10 13:55 ` Steve Dibb [this message]
2007-10-10 15:39 ` [gentoo-dev] " Duncan
2007-10-12 6:26 ` Steve Long
2007-10-12 10:35 ` Marijn Schouten (hkBst)
2007-10-12 15:44 ` Duncan
2007-10-12 12:06 ` Duncan
2007-10-13 0:22 ` Chris Gianelloni
2007-10-13 10:37 ` Duncan
2007-10-13 16:20 ` Chris Gianelloni
2007-10-13 19:52 ` [gentoo-dev] " Steve Long
2007-10-10 19:19 ` [gentoo-dev] " Chris Gianelloni
2007-10-10 7:49 ` George Shapovalov
2007-10-10 12:45 ` Petteri Räty
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=470CD9B5.3000706@gentoo.org \
--to=beandog@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