[pkg-nvidia-devel] Bug#558434: Bug#558434: libvdpau1 should not depend on the libvdpau-driver metapackage
superm1 at ubuntu.com
Sun Nov 29 05:12:52 UTC 2009
I think we've got a few disconnects here still.
> libvdpau without a vdpau driver is not very useful, thus the reason why
> libvdpau1 depends on libvdpau-driver.
I'd argue against this. Binary packages can then link against this package
without having to pull in the full VDPAU implementation which is a big win.
> Seeing that the nvidia vdpau driver is the only vdpau driver implementation
> available, that's why you see libvdpau-driver have only one dependency.
> more vdpau driver implementations are available, libvdpau-driver will be
> updated and users may freely choose what vdpau driver they want to use, or
> install all of the drivers (libvdpau can handle picking a suitable driver),
> simply let apt install the default vdpau driver (the first package in the
> Depends field out of all the alternatives). Also, once a free vdpau
> implementation becomes available, libvdpau can enter main.
Does Debian allow different sections for different binary packages from the
same source package? Perhaps for now you can then leave libvdpau-driver in
contrib and the rest in main so other packages in main can start taking
advantage of this sooner since there is no ETA for an Intel or AMD VDPAU
> Also, nvidia-glx doesn't depend on any of the libvdpau packages so
> nvidia-glx won't install libvdpau.
> I'm surprised this isn't the case already for Debian. I saw this in the
Ubuntu packages for NVIDIA, so I expected it was the same here. Is there
any reason *not* to do this? At least as a Recommends. The NVIDIA closed
source VDPAU implementation library makes little to no sense by itself, and
then users don't have to go through the extra step to install it if they
want to use it.
superm1 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pkg-nvidia-devel