| 1 |
On Saturday, July 31, 2010 14:27:14 Jacob Godserv wrote: |
| 2 |
> Honestly not sure what convention is for naming, but I found this |
| 3 |
> recently, and thought I might throw it out there: |
| 4 |
> |
| 5 |
> ~ $ euse -i lame |
| 6 |
> .... |
| 7 |
> [+ C ] lame - Prefer using LAME libraries for MP3 encoding support |
| 8 |
> .... |
| 9 |
> |
| 10 |
> While, as a user, I prefer this to be mp3, I also understand there may |
| 11 |
> be more than one library for such-and-so, so I'm willing to read up on |
| 12 |
> USE flags to find out which is the best to use. Overall, I would prefer |
| 13 |
> naming according to the names of the libraries they'll enable. |
| 14 |
|
| 15 |
that example isnt relevant. notice how the description includes the word |
| 16 |
"prefer" and isnt just "enable mp3 support". |
| 17 |
|
| 18 |
USE=mp3 is how you get mp3 support. if there are multiple options (like |
| 19 |
ffmpeg or lame or mpg123 or something else), then USE=lame shows up to select |
| 20 |
one particular implementation over another. but it would still be: |
| 21 |
USE="mp3 lame" |
| 22 |
-mike |
Archives