Hi Anres:<div><br><div class="gmail_quote">On Sat, Nov 28, 2009 at 18:56, Andres Mejia <span dir="ltr"><<a href="mailto:mcitadel@gmail.com">mcitadel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Saturday 28 November 2009 17:09:21 Mario Limonciello wrote:<br>
> Package: libvdpau<br>
> Version: 0.3-1<br>
> Severity: normal<br>
><br>
> Currently, libvdpau1 depends on libvdpau-driver which in turn only depends<br>
> upon an NVIDIA closed source library.<br>
><br>
> This means that any package that depends on libvdpau1 to be able to<br>
> optionally provide support for VDPAU will depend on the NVIDIA library.<br>
> The dependency should be dropped, and individual packages that will<br>
> "require" VDPAU support should depend upon the driver package.<br>
<br>
</div>The idea with the libvdpau-driver was for it to depend on the multiple<br>
implementations of the vdpau driver that may exist. It would have a Depends<br>
field like.<br>
<br>
Depends: ati-libvdpau1-driver |<br>
intel-libvdpau1-driver |<br>
. . .<br>
nvidia-libvdpau1-driver [amd64 i386]<br>
<br>
In this way, only one package (libvdpau-driver) has to be updated when a new<br>
vdpau driver implementation is available, rather than updating however many<br>
packages that may depend on libvdpau1.<br>
<br></blockquote><div><br></div><div>This i'm not arguing with. I think it's a great idea to have such a metapackage, I just don't think the metapackage should be an explicit dependency of libvdpau1. Some apps (i'm looking at mythtv and mplayer here) can build with vdpau support, but work just fine in other modes. So look at this hypothetical situation for how it is today:</div>
<div><br></div><div>Lets say I'm on an intel graphics system. There's no VDPAU support yet on Intel.</div><div><br></div><div>1) You build-depends mplayer on libvdpau-dev. It gets VDPAU support.</div><div>2) Via shlibdeps, mplayer's binary package now depends upon libvdpau1.</div>
<div>3) libvdpau1 depends on libvdpau-driver.</div><div>4) libvdpau-driver pulls in the non-free nvidia vdpau stuff</div><div><br></div><div>That non-free nvidia stuff isn't desirable on such a system. If you were to however go and say build an NVIDIA rig, the NVIDIA glx package would pull in the vdpau things automatically and you'd be able to benefit from VDPAU then.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
-- </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Regards,<br>
<font color="#888888">Andres<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Mario Limonciello<br><a href="mailto:superm1@gmail.com">superm1@gmail.com</a><br>
</div>