> For the foreseeable future, the only viable approach is to allow the
> user to explicitly enable or disable such features.
Then I guess the best that can be done is to ensure that
GRASS_NO_GLX_PIXMAPS and GRASS_NO_GLX_PBUFFERS are widely documented.
Would it be best to set them for now until conditions improve to
minimize user impact?
I suggest putting that question to the mailing list(s).
If they are disabled by default, the variable names should probably
have the "NO_" removed, and accept 0/1 values, e.g.
GRASS_GLX_PIXMAPS=0 # force off
GRASS_GLX_PIXMAPS=1 # force on
# anything else = default = off for now, on if the feature eventually
# becomes usable on the majority of systems
--
Brad Douglas <rez touchofmadness com> KB8UYR
Address: 37.493,-121.924 / WGS84 National Map Corps #TNMC-3785
> > For the foreseeable future, the only viable approach is to allow
> > the user to explicitly enable or disable such features.
>
> Then I guess the best that can be done is to ensure that
> GRASS_NO_GLX_PIXMAPS and GRASS_NO_GLX_PBUFFERS are widely
> documented. Would it be best to set them for now until conditions
> improve to minimize user impact?
I suggest putting that question to the mailing list(s).
If they are disabled by default, the variable names should probably
have the "NO_" removed, and accept 0/1 values, e.g.
GRASS_GLX_PIXMAPS=0 # force off
GRASS_GLX_PIXMAPS=1 # force on
# anything else = default = off for now, on if the feature eventually
# becomes usable on the majority of systems
I suggest that the default for 6.2 should be "off" (ship a working
product), for 6.3 it should be "on" (it IS a dev version...). If "off"
for 6.3 I think this will never be fixed.
and testing for "0" || "FALSE" and "1" || "TRUE" is nice,