[Mesa3d-dev] [PATCH 0/2] Keep generated glapi sources in mesa
dbn.lists at gmail.com
Fri Feb 15 07:52:40 PST 2008
On Thu, Feb 14, 2008 at 9:57 AM, Daniel Stone <daniel at fooishbar.org> wrote:
> On Thu, Feb 14, 2008 at 09:44:28AM -0800, Dan Nicholson wrote:
> > On Thu, Feb 14, 2008 at 9:34 AM, Daniel Stone <daniel at fooishbar.org> wrote:
> > > On Thu, Feb 14, 2008 at 09:14:09AM -0800, Ian Romanick wrote:
> > > > We used to do this before, back in the pre-modular days. The problem,
> > > > if I recall, was that when changes were made to GLX protocol code people
> > > > had to keep their Mesa and X.org trees in lock-step. Everyone hated that.
> > >
> > > I'm not really seeing the difference between then and now.
> > Caveat: I'm not going to try to pretend that I understand the GLX API at all.
> > In the current case it is worse (as far as I can tell). If the GLX API
> > changes in mesa, you then have to wait for someone to sync the
> > server-side files into xserver. With these patches, the changes are at
> > least localized to a single commit in mesa. Whether libglx can cope
> > with changes in the API wouldn't seem to be affected in either case.
> Indeed. My point was that you still have to keep your Mesa and X.Org
> trees in lockstep today (and as Dan points out, this actually improves
> the situation): every time a file is added, removed, or renamed, which
> seems to be roughly every second week, the build system needs updating.
> And people still hate it.
Unless anyone has anyone has any further objections, I'll be pushing
these to mesa and xserver within the next day or so. Ian, are you
still concerned about this?
More information about the xorg