This ebuild provides the VDPAU backend for libva. Reproducible: Always
Created attachment 229255 [details] Proposed ebuild
(In reply to comment #1) > Created an attachment (id=229255) [details] > Proposed ebuild I think you have to depend on some that provides vdpau (I think this is x11-drivers/nvidia-drivers). For opengl, you have to depend on virtual/opengl. There's also a --enable-tracer switch. Maybe it is useful to add a use flag for it (I suppose it has something to do with debugging, so maybe not everybody want it installed, so it's your call)
added, thanks under x11-libs/vdpau-video, i dont understand why you wanted to change the name
No ~x86 support?
(In reply to comment #3) > under x11-libs/vdpau-video, i dont understand why you wanted to change the name “vdpau-video” is pretty much a plugin to libva (vdpau-video depends on libva, while at the same time client apps don't use it directly but through libva). Thus I though “libva-vdpau” is much clearer to that respect - “vdpau-video” doesn't really say much as a name.
(In reply to comment #2) > I think you have to depend on some that provides vdpau (I think > this is x11-drivers/nvidia-drivers). Actually, vdpau-video asks the display driver for the name of a shared library. So if the user uses a driver that supports VDPAU, it should just work. Otherwise no VDPAU. So it's up to the user to choose a proper driver. And, conceivably, the vdpau use flag could be set without the user having capable hardware/wishing to use a driver providing it (eg if only proprietary drivers do). What good would be a dependency then? Would just pull in a driver that's not needed or wanted or used.
