On Thu, 17 May 2001, Will Newton wrote:

>> Unfortunately, until 4.x supports all the hardware, or at least
>> the hardware that we consider important, we need to ship 3.3.6
>> servers in addition to 4.x, and that has some really crummy side
>> effects, like having to ship separate Mesa and other hacks so
>> that everyone can do 3D.  I would like nothing more than to get
>> rid of XFree86 3.3.6 from the distribution, and also the separate
>> Mesa package.
>
>Maybe this is a silly question, but couldn't it be setup so XFree86 >= 4.0
>conflicts with Mesa, and Xfree86 < 4.0 requires it? That way surely you
>could make standalone Mesa for those who have old XFree and no DRI? Or is
>there a sane configuration that mixes XFree 3.3.x and 4.x?

Our current setup AFAIK is the only way to allow XFree86 4.x and
3.3.6 to coreside and both do software OpenGL, as well as
allowing DRI to work where supported.  We need users to be able
to switch between 4.x and 3.3.6 without installing/uninstalling a
bunch of stuff which means that this is necessary until 3.3.6 is
no longer needed.  Otherwise we must cripple our 3.3.6 support in
order to use the Mesa that comes as part of XFree86.

Yes, the solution is a horrible hack, but it does work fairly
transparently for the most part.

I will be assimilating the separate Mesa package to be inside our
XFree86-4.x SRPM very shortly also - to minimize some other build
related problems that have come up as well.


----------------------------------------------------------------------
Mike A. Harris                  Shipping/mailing address:
OS Systems Engineer             190 Pittsburgh Ave., Sault Ste. Marie,
Red Hat Inc.                    Ontario, Canada, P6C 5B3
http://www.redhat.com           Phone: (705)949-2136
----------------------------------------------------------------------
Latest XFree86 test RPMS:      ftp://people.redhat.com/mharris/testing


_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to