1 |
El lun, 19-01-2015 a las 23:40 +0100, Michał Górny escribió: |
2 |
> Dnia 2015-01-19, o godz. 23:09:55 |
3 |
> Rémi Cardona <remi@g.o> napisał(a): |
4 |
> |
5 |
> > Why not : |
6 |
> > |
7 |
> > libav? ( media-libs/libav:= ) |
8 |
> > ffmpeg? ( media-libs/ffmpeg:= ) |
9 |
> > |
10 |
> > + REQUIRED_USE="^^ ( libav ffmpeg )" |
11 |
> > |
12 |
> > I for one would never expect USE=-libav to enable ffmpeg (nor |
13 |
> > USE=-ffmpeg to enable libav FWIW). |
14 |
> |
15 |
> Two reasons: |
16 |
> |
17 |
> 1. Compatibility. USE=ffmpeg is already used for || ( libav ffmpeg ) in |
18 |
> a lot of packages. If we changed the meaning, libav users will end up |
19 |
> switching '-ffmpeg libav' per-package. Ugly. |
20 |
> |
21 |
> 2. Feature-oriented flags. USE=ffmpeg represents the generic feature, |
22 |
> USE=libav is auxiliary implementation-switch flag. Well, maybe we could |
23 |
> use, say, USE=avcodec to avoid ambiguity but that's a larger change. |
24 |
> |
25 |
> |
26 |
|
27 |
I agree with your suggestion but I would prefer the Remi's approach of |
28 |
letting people to know if they want "ffmpeg" or "libav", otherwise it is |
29 |
not so obvious to know what disabling/enabling one of that USE flags |
30 |
will end up causing without reading each ebuild :/ (also, maybe some |
31 |
ebuilds will use one logic while others the inverse) |