| 1 |
On Fri, 2006-07-14 at 05:03 +0100, Daniel Watkins wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> It seems to me that having both of these two flags can only cause confusion. |
| 6 |
> I upgraded xine-lib yesterday and spent a very frustrating 2 hours trying |
| 7 |
> to work out what had broken my Amarok MP3 playback. It turns out that |
| 8 |
> having the 'mp3' USE flag set globally is not good enough to get MP3 |
| 9 |
> playback enabled in xine-lib, you need 'mad' set. |
| 10 |
> |
| 11 |
> Is there a rationale behind this decision? If not, it would seem to be quite |
| 12 |
> an important issue, as a lot of users will be looking for MP3 playback (and |
| 13 |
> expecting it to work from one version of xine-lib to the next, without |
| 14 |
> having to play with USE flags). |
| 15 |
|
| 16 |
I think the problem is that the flags have started to become used for |
| 17 |
different things. It *used* to be like this: |
| 18 |
|
| 19 |
mp3 - enabled mp3 support |
| 20 |
mad - used libmad over $whatever for mp3 playback |
| 21 |
|
| 22 |
What this meant was simple. If a package *only* used libmad, then |
| 23 |
USE=mp3 would enable it. The *only* reason you would use USE=mad is if, |
| 24 |
for example, a package used libmpeg3 *or* libmad, to select between the |
| 25 |
two. Some people have started to interpret the "this package uses |
| 26 |
libmad" as "you need USE=mad for mp3 support" which, in my opinion, is |
| 27 |
wrong. |
| 28 |
|
| 29 |
If a user has USE="mp3 -mad" then they should *always* have working mp3 |
| 30 |
support. |
| 31 |
|
| 32 |
-- |
| 33 |
Chris Gianelloni |
| 34 |
Release Engineering - Strategic Lead |
| 35 |
x86 Architecture Team |
| 36 |
Games - Developer |
| 37 |
Gentoo Linux |
Archives