Re: Bug#94114: mesag3-glide2: mesag3-glide2 needs MESA_GLX_FX
>> Herbert Xu <firstname.lastname@example.org> writes:
> On Mon, Apr 16, 2001 at 12:08:27PM +0200, Marcelo E. Magallon wrote:
> > > There is no alternative to setting the environment variable MESA_GLX_FX.
> > Yes. What do you suggest I do? If you read README.3DFX you'll see
> > there's no reasonable default, is there? And the environment variable
> > is read by the library, no by your application.
> nsswitch.conf is read by a library, so there is clear precedence where a
> library reads a configuration file.
I never said that's not possible. I'm just saying this is not the way
*this* library works. Since I don't use this particular feature of
Mesa, I don't know why this is so. If you read README.3DFX you'll note
this is the least interesting environment variable there is. It has
three possible values, and none is a good default, because, AFAICS,
it's hardware and configuration dependent.
> > I'll willing to argue I don't have to follow policy on this one. It is
> > clear that this policy is meant for application programs, not libraries.
> I disagree. There is no dinction nor the intent to disguinsh between
> programs and libraries in the policy.
If a program usually depends on environment variables for its
configuration, the program should be changed to fall back to a
reasonable default configuration if these environment variables
are not present.
My point is there is no "reasonable default". The choices are
fullscreen (which might not make sense if you have only one monitor),
windowed (which is slow) and disabled (which, err... isn't the reason
why you bought the card in the first place).
Policy is oriented towards programs, it even suggests the use of a
wrapper for those circumstances where it's "difficult" to change the
Anyways, I can fix this, but don't expect it to happen soon. This is
not the only variable that's used by Mesa.