From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: lame use flag, local to global
Date: Fri, 12 Oct 2007 12:35:30 +0200 [thread overview]
Message-ID: <470F4DF2.8020205@gentoo.org> (raw)
In-Reply-To: <fen3qr$lu6$1@sea.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steve Long wrote:
> Duncan wrote:
>
>> Steve Dibb <beandog@gentoo.org> posted 470CD9B5.3000706@gentoo.org,
>> excerpted below, on Wed, 10 Oct 2007 07:55:01 -0600:
>>
>>> 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.
>> In that case, shouldn't the description mention that? Something like:
>>
>> MP3 encoding support using LAME (as opposed to ffmpeg)
>>
> What about when the next one gets added-- would it need to say "as opposed
> to ffmpeg or lame"?
>
> I agree where there's a choice, the ebuild should offer lame or ffmpeg or
> w/e, and where not simply mp3 (along with the encode/decode being
> orthogonal.)
what about mp3=lame or mp3=ffmpeg? This will also be easily extendable when
the next implementations comes along (mp3=newmp3lib).
Marijn
- --
Marijn Schouten (hkBst), Gentoo Lisp project
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHD03xp/VmCx0OL2wRAgIxAJ47l1Y0IdL3n/GGKPYoiYW2Ec/IAwCeIDxp
mNGh5idhB7qUVEDQb3Y65sI=
=dwdN
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-12 10:45 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
2007-10-10 15:39 ` [gentoo-dev] " Duncan
2007-10-12 6:26 ` Steve Long
2007-10-12 10:35 ` Marijn Schouten (hkBst) [this message]
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=470F4DF2.8020205@gentoo.org \
--to=hkbst@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