On Mon, Jan 19, 2015 at 4:40 PM, Michał Górny <[email protected]> wrote:
> Dnia 2015-01-19, o godz. 23:09:55 > Rémi Cardona <[email protected]> napisał(a): > > > Why not : > > > > libav? ( media-libs/libav:= ) > > ffmpeg? ( media-libs/ffmpeg:= ) > > > > + REQUIRED_USE="^^ ( libav ffmpeg )" > > > > I for one would never expect USE=-libav to enable ffmpeg (nor > > USE=-ffmpeg to enable libav FWIW). > > Two reasons: > > 1. Compatibility. USE=ffmpeg is already used for || ( libav ffmpeg ) in > a lot of packages. If we changed the meaning, libav users will end up > switching '-ffmpeg libav' per-package. Ugly. > > There are only 61 packages with USE="ffmpeg", and quite few of those might reasonably have package.use different from make.conf. > 2. Feature-oriented flags. USE=ffmpeg represents the generic feature, > USE=libav is auxiliary implementation-switch flag. Well, maybe we could > use, say, USE=avcodec to avoid ambiguity but that's a larger change. So, it is then expected to have both (USE="ffmpeg libav") to enable the feature and then select the implementation? That's quite counter-intuitive, and in some cases, there are some significant API differences - it is not just a drop-in "auxiliary implementation".
