Re: [Dri-devel] DRI-/Mesa-CVS is totally broken after Mesa "update"

[Michel <mi...@da...>]

On Fri, 2004-03-12 at 20:34, Ian Romanick wrote:
> Jon Smirl wrote:
> 
> > Sorry I broke the DRI build, now I see what the problem is. When the Mesa is
> > included in the DRI tree is it is using the DRM driver in the DRI tree. I didn't
> > know that the DRI build would alter the Mesa include paths. 
> 
> Ugh.  In the future, if people are going to do something that will alter 
> build processes, the ramifications need to be discussed and agreed upon 
> by other developers.  Silence != approval.  Stuff like this makes good 
> topics for the weekly IRC meetings. :)

Indeed.


> > I have pile of changes ready that require simultaneous changes in 
> > mesa and the drm driver. For me it would be much simpler to have the
> > DRM driver and mesa in the same tree. I'm targeting this work to go
> > into xserver, not xfree.

I don't see how that matters; same DRM. (BTW, the DRM in the DRI tree
isn't 'a copy', it's The Original(TM) :)

> > But other people want to keep the DRM in the DRI tree. Doing this means I have
> > to be careful about doing parallel check-ins to both trees. 

Which is a good thing, because it should help keep the interface clean.

> > It also forces me to work in the DRI tree, a tree that I'm not using.
> 
> I don't think anyone *really* wants to keep it in the DRI tree.  I think 
> most folks want it in its own tree.  

Yes. Once the userspace drivers have moved to the Mesa and X trees,
there won't be much more left anyway. :)

> Perhaps now would be a good time to forge ahead on that front as well.
> Dunno.

The sooner the better IMHO. Any takers?


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer