Official method for determining modular X module path?

[Donnie Berkholz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andy Ritger wrote:
| In the short term, a compromise to allow multiple libGL's to coexist
| on the file system might be a system where:
|
|     - distributions provide a simple utility (let's call
|       it `/usr/bin/select-opengl.sh`; invoked, perhaps like
|       `select-opengl.sh nvidia`).  Such a tool would:
|
|         - update /etc/ld.so.conf so that the correct OpenGL
|           implementation's directory was prepended to the library
|           search path
|
|         - symlinked /usr/lib/libGL.so.1 to the requested OpenGL
|           implementation (to provide backwards compatibility for
|           applications that dlopen() a specific libGL); this point
|           might be debatable/unnecessary.
|
|       We could provide a sample implementation of select-opengl.sh,
|       but distributions would be free to implement it however they
|       like, such as with environment modules, as suggested in the
|       OpenGL ABI discussion mentioned above.

Feel free to build on Gentoo's opengl-update script (and now
eselect-opengl, using a new framework), assuming the license stays the
same. =)

IMHO, Gentoo has perhaps the best handling of 3rd-party drivers among
distributions I'm aware of.

Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDjrOBXVaO67S1rtsRAiYNAKDupZC37RgyhlMILPGU0VfR8GOjCgCg2mYI
wmGIAiZaYhCu4kxONBgA2rc=
=gmzJ
-----END PGP SIGNATURE-----