On Saturday, July 31, 2010 16:02:51 Steve Dibb wrote: > On 07/31/2010 12:51 PM, Mike Frysinger wrote: > > On Saturday, July 31, 2010 14:27:14 Jacob Godserv wrote: > >> Honestly not sure what convention is for naming, but I found this > >> > >> recently, and thought I might throw it out there: > >> ~ $ euse -i lame > >> > >> .... > >> [+ C ] lame - Prefer using LAME libraries for MP3 encoding support > >> .... > >> > >> While, as a user, I prefer this to be mp3, I also understand there may > >> be more than one library for such-and-so, so I'm willing to read up on > >> USE flags to find out which is the best to use. Overall, I would prefer > >> naming according to the names of the libraries they'll enable. > > > > that example isnt relevant. notice how the description includes the word > > "prefer" and isnt just "enable mp3 support". > > The description is misleading, and needs to be changed. Just because > something has an mp3 and a lame use flag, it does not mean that flipping > on lame means that the application will prefer lame over mad or mpg123.
sounds like a bug in the package, or the package metadata.xml needs updating. the current lame desc sounds fine to me. -mike
signature.asc
Description: This is a digitally signed message part.
