[pkg-nvidia-devel] Bug#594298: libgl1-nvidia-alternatives: alternatives are very strange and probably not correct
Andreas Beckmann
debian at abeckmann.de
Wed Aug 25 07:23:32 UTC 2010
On 2010-08-25 08:56, Norbert Preining wrote:
> /etc/alternatives/libGL.so -> /usr/lib/nvidia/diversions/libGL.so
> /usr/lib/nvidia/diversions/libGL.so -> libGL.so.1
> /usr/lib/nvidia/diversions/libGL.so.1 -> libGL.so.1.2
> that seems to be MESA
>
> /etc/alternatives/libGL.so.1 -> /usr/lib/nvidia/libGL.so.1
> /usr/lib/nvidia/libGL.so.1 -> libGL.so.195.36.31
> that seems to be NVIDIA
>
> Should that work???
The intention behind this is:
if you compile and link something, use the MESA headers and libs, so you
get binaries that work everywhere (because you don't accidently use some
nvidia-only symbols). Shlibs are configured to produce dependencies on
the MESA libs only. Building packages with libgl1-nvidia-glx will
produce dependencies on the free libgl1-mesa-glx only.
libgl1-nvidia-glx can't provide libgl1 because of the dependencies
declared in the libgl1-mesa-* packages - and we explicitly want to allow
them to be installed in parallel to libgl1-nvidia-*.
But when actually running the programs, you probably want to use the
accelerated nvidia libGL if it is installed, so libgl.so.1 points to nvidia.
Some documentation of all the things will needed ...
Andreas
More information about the Pkg-nvidia-devel
mailing list