Not sure if this is really an issue. But after reading #534128 I noticed that there *is* some confusion about the name of this config file. eslect opengl creates a file /etc/X11/xorg.conf.d/20opengl.conf while other files use a hyphen (e.g. 97-evdev.conf). On some systems (noticed this on mine, reading the bugreport I mentioned earlier it appears that others have similar issues) a file called 20-opengl.conf exists. Eventually the name was changed in the utility along the way, creating two configs that might overwrite each other and cause opengl issues. I would suggest that an updated version of eselect checks for 20opengl.conf and known hashes and warns the user [1]. And that it uses 20-opengl.conf by default to stay consistent with the other files. Best wishes, Michael [1] When invoked: - Just delete the file 20opengl.conf if the md5sum is 02f2b21130b93a2bb6662ac125884077 (Add known md5 for nvidia / ati settings) - If md5 unknown, print: "eselect detected that /etc/X11/xorg.conf.d/20opengl.conf exists and contains custom settings. You can migrate your settings to 20-opengl.conf and delete 20opengl.conf" - write new config to 20-opengl.conf
eselect opengl also creates /etc/env.d/000opengl and not 00opengl as one would expect.
(In reply to Jesper Olsson from comment #1) > eselect opengl also creates /etc/env.d/000opengl and not 00opengl as one > would expect. This is needed to make it sourced before 00basic.
I am not sure if this means, that this mix(?) is intentional. Either way, I assume this bugreport is no longer relevant so I'll just close it. :-)
