[pkg-nvidia-devel] Bug#594298: Bug#594298: Bug#594298: Bug#594298: libgl1-nvidia-alternatives: alternatives are very strange and probably not correct

[Russ Allbery]

Norbert Preining <preining at logic.at> writes:
> On Mi, 25 Aug 2010, Andreas Beckmann wrote:

>> Then they need a dependency on libgl1-mesa-dev | libgl1-dev |
>> libgl1-dev. Eventually somebody would notice that this is BAD. Even

> I'm not speaking about Debian programs, but third party, like games
> from LOKI, or LGP, or some others.

> A quick strings | grep libGL over Descent3 from loki showed me:
> /usr/local/games/Descent3] strings * | grep libGL
> /usr/lib/libGL.so
> Specify path to libGL.so:
> libGL.so
> libGL.so.1
> libGL.so.1
> libGL.so
> libGL.so.1
>       working. Use the same libGL.so that you'd use for Quake 3. Glide also
>      library. The default is libGL.so (or libGlide2x.so) from your library
>   - If the default libGL or user-specified libGL fails to load, 1.4.0a will
>     try libGL.so.1 as a last resort...

> which might indicate that they are actually opening libGL.so, and only if
> that is not there libGL.so.1.

> Didn't check the others I have installed.

Note, though, that the average Debian user isn't going to have any
libGL.so link at all, since to get it they'd have to install GL dev
packages.  So this logic would actually work most of the time.

If we do get bug reports of this not working for people, though, we can
rethink.  In talking to people who knew more about GL than I did,
apparently the risk of picking up NVIDIA symbols from linking against
libGL.so is not high.  It would require people writing GL code in a
completely incorrect way that the GL standard says you're not supposed to
do.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>