| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Steve Long wrote: |
| 5 |
> Duncan wrote: |
| 6 |
> |
| 7 |
>> Steve Dibb <beandog@g.o> posted 470CD9B5.3000706@g.o, |
| 8 |
>> excerpted below, on Wed, 10 Oct 2007 07:55:01 -0600: |
| 9 |
>> |
| 10 |
>>> The reason we have mp3 and lame use flag is because there is more than |
| 11 |
>>> one mp3 encoder. In almost every case of the use flag being applied |
| 12 |
>>> above, there is already support for another mp3 codec (ffmpeg). So, |
| 13 |
>>> lame adds support for lame, not for mp3, which is also provided. |
| 14 |
>> In that case, shouldn't the description mention that? Something like: |
| 15 |
>> |
| 16 |
>> MP3 encoding support using LAME (as opposed to ffmpeg) |
| 17 |
>> |
| 18 |
> What about when the next one gets added-- would it need to say "as opposed |
| 19 |
> to ffmpeg or lame"? |
| 20 |
> |
| 21 |
> I agree where there's a choice, the ebuild should offer lame or ffmpeg or |
| 22 |
> w/e, and where not simply mp3 (along with the encode/decode being |
| 23 |
> orthogonal.) |
| 24 |
|
| 25 |
what about mp3=lame or mp3=ffmpeg? This will also be easily extendable when |
| 26 |
the next implementations comes along (mp3=newmp3lib). |
| 27 |
|
| 28 |
Marijn |
| 29 |
|
| 30 |
- -- |
| 31 |
Marijn Schouten (hkBst), Gentoo Lisp project |
| 32 |
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 35 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 36 |
|
| 37 |
iD8DBQFHD03xp/VmCx0OL2wRAgIxAJ47l1Y0IdL3n/GGKPYoiYW2Ec/IAwCeIDxp |
| 38 |
mNGh5idhB7qUVEDQb3Y65sI= |
| 39 |
=dwdN |
| 40 |
-----END PGP SIGNATURE----- |
| 41 |
-- |
| 42 |
gentoo-dev@g.o mailing list |
Archives