Folks, I'm working on a rearrangement of the proprietary nVidia drivers to separate the generic VDPAU interface from the nVidia package. I'm doing this in my own repository (see libvdpau, vdpauinfo, and nvidia in smerp.rpath....@rpl:2). I had a couple of questions regarding this:
1. The current way I'm dealing with the fact that the 185.x.x drivers ship their own libvidpau.so* and libvdpau_trace.so* (as well as headers) is to remove them from the distribution before installing. Is this adequate? 2. libvdpau is neither dependent upon nvidia:lib, nor vice versa. This enables applications (e.g. xbmc, ffmpeg, etc.) to compile against libvdpau as a standalone shared library as it was intended allowing for the driver-specific VDPAU libs (e.g. libvdpau_nvidia.so, which IS distributed in nvidia:lib) at runtime. Kosher? 3. Should packages compiled with VDPAU support be flavored as such, or should we just compile the support in regardless? My understanding is that VDPAU support can be compiled in, and if no suitable "backend" library is found, that it should gracefully degrade. If my understanding is wrong, I'd imagine the right thing to do would be to flavor such packages as vdpau and flavor the nvidia drivers as ~vdpau. Right? Let me know. None of this is going into 2-devel without some discussion. --smerp _______________________________________________ Foresight-devel mailing list [email protected] http://lists.rpath.org/mailman/listinfo/foresight-devel
