| 1 |
lör 2010-07-31 klockan 13:37 +0200 skrev Hanno Böck: |
| 2 |
> vpx for supporting googles vp8 codec used in webm. |
| 3 |
> |
| 4 |
> At the moment this is only mplayer and ffmpeg, but it's pretty obvious that |
| 5 |
> apps supporting vp8 will start popping up everywhere (currently working on |
| 6 |
> arista ebuild which will support it). |
| 7 |
> |
| 8 |
> Though we might discuss if vpx is really a good name or it shouldn't be vp8. |
| 9 |
> |
| 10 |
|
| 11 |
This feels like the standard discussion about a use flag for function |
| 12 |
versus a use flag for dependencies. |
| 13 |
|
| 14 |
Myself I think this should follow the most commonly for ssl found |
| 15 |
nameing convention which is that: |
| 16 |
|
| 17 |
USE="ssl" provides ssl support in all packages. If a package has |
| 18 |
optional ssl-support they should have this flag. |
| 19 |
|
| 20 |
USE="gnutls openssl nss ..." finetunes which implementation of ssl to |
| 21 |
use. They should never exist without USE="ssl" unless they package has |
| 22 |
unconditional ssl support. |
| 23 |
|
| 24 |
|
| 25 |
Of course there are people who think otherwise even for ssl/tls, and so |
| 26 |
you cannot be sure that you have ssl/tls support even if you have |
| 27 |
USE="ssl". |
| 28 |
For example if you cannot connect with vnc using tls to your qemu |
| 29 |
virtual machine then you have to look up that ebuild to see that tls is |
| 30 |
only enabled if you have USE="gnutls". I think that is suboptimal and |
| 31 |
confusing for the user. |
| 32 |
|
| 33 |
|
| 34 |
So I think a USE="vp8" or USE="webm" (probably the first) to enable |
| 35 |
decoding, and USE="vpx" should be used to fine tune what implementation |
| 36 |
to use. Having USE="vp8" (no USE="vpx" specified) in make.conf should |
| 37 |
give you support for vp8 in all packages and the implementation should |
| 38 |
be the maintainers preference for that package. |
Archives