Subject: Re: Mesa-glx versus xlockmore?
To: Mason Loring Bliss <>
From: Andrew Gillham <>
List: tech-pkg
Date: 10/10/1999 01:34:57
Mason Loring Bliss writes:
> On Fri, Oct 08, 1999 at 06:57:11PM -0400, Mason Loring Bliss wrote:
> > Well... We'll know if it works by this evening, then, and if it doesn't work,
> > I'll try to figure out what's different between this and my old setup.
> Hm. Well, having "GLX_CHIPSET=tnt" in /etc/mk.conf didn't seem to do the
> trick. I'll bang on it tomorrow, I guess, and see what's not happening.

It did for me.  There is an error in the pkgsrc/graphics/Mesa/Makefile
that says "CONFLICT=" instead of "CONFLICTS=" which will cause things
that depend on 'Mesa-*' to re-install Mesa (software only) over top of
your Mesa-glx-* package.

What could be happening is you install Mesa-glx-tnt-*, and then build/install
xlockmore, which causes the Mesa-3.0 to be installed.  Your end result is
software GL again. :)

On my system 'xlock -modelist allgl +sequential' is very fast and nice.

Andrew Gillham                            | This space left blank                     | inadvertently.
I speak for myself, not for my employer.  | Contact the publisher.