On Fri, 2006-07-14 at 05:03 +0100, Daniel Watkins wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > It seems to me that having both of these two flags can only cause confusion. > I upgraded xine-lib yesterday and spent a very frustrating 2 hours trying > to work out what had broken my Amarok MP3 playback. It turns out that > having the 'mp3' USE flag set globally is not good enough to get MP3 > playback enabled in xine-lib, you need 'mad' set. > > Is there a rationale behind this decision? If not, it would seem to be quite > an important issue, as a lot of users will be looking for MP3 playback (and > expecting it to work from one version of xine-lib to the next, without > having to play with USE flags).
I think the problem is that the flags have started to become used for different things. It *used* to be like this: mp3 - enabled mp3 support mad - used libmad over $whatever for mp3 playback What this meant was simple. If a package *only* used libmad, then USE=mp3 would enable it. The *only* reason you would use USE=mad is if, for example, a package used libmpeg3 *or* libmad, to select between the two. Some people have started to interpret the "this package uses libmad" as "you need USE=mad for mp3 support" which, in my opinion, is wrong. If a user has USE="mp3 -mad" then they should *always* have working mp3 support. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
