Dnia 2015-02-02, o godz. 18:08:01 Ulrich Mueller <[email protected]> napisał(a):
> >>>>> On Mon, 2 Feb 2015, Alexis Ballier wrote: > > > On Mon, 2 Feb 2015 17:14:22 +0100 > > Ulrich Mueller <[email protected]> wrote: > > >> Why? When you have USE="-ffmpeg", the libav flag is a "don't care" > >> which is ignored. "ffmpeg" controls the feature, "libav" chooses > >> the implementation. This is very clear from the flags' descriptions > >> and was also well explained in the (N-1) news item. > > > Would you offer me a beer each time I'll point you at some user > > doing USE='-ffmpeg libav' because he wants libav only ? :) > > "-ffmpeg libav" is a valid combination, given that "ffmpeg" can be set > per-package, whereas typically there would be only a global setting of > "libav". It is quite a similar situation to what we had with openmotif > and lesstif, where the motif flag enabled the feature, and the lesstif > flag chose the implementation. It is valid but USE=libav is then unexpectedly meaningless :). This thread alone shows how confused users are by it. > Or is it the name of the flag that is causing confusion? That could be > changed. Maybe. But there's no good solution for that either. My USE=avcodec idea brought many complaints... But even then, regular USE flags for this kind of global switch don't work well. Maybe we should do the Arfrever thing. USE=ffmpeg-or-libav and USE=ffmpeg-instead-of-libav. This will avoid most of the confusion, though ffmpeg users will complain that we don't have USE=libav-instead-of-ffmpeg instead. -- Best regards, Michał Górny
pgpHfJ_0thvus.pgp
Description: OpenPGP digital signature
