MESA 6.0 was released on 16.Jan. 2003 Would be nice to see it in portage, because the latest release in portage seems to be 3.5 (?? quite old, but the only mesa i could find) Reproducible: Always Steps to Reproduce: 1. 2. 3.
Yeah, we haven't been supplying an external mesa because xfree86 provides its own, and that's about the only use for mesa in portage at present. Do you have any reason it should be in portage? I imagine you noticed the one in portage right now is masked, also.
i do not have any (good) reason for an ebuild. i was just playing around emerging torcs (which failes because of some glu-errors while emerging plib). so i searched portage, found out that it seemed to be part of the mesa project. a look at the website told me, that verion 6.0 was released an portage only has 3.5. so i was wondering. but if xfree86 comes with its own mesa, the problem of emerging plib hs nothing to do with this external version of mesa. The only good reason might be the oportunity for the user to choose another mesa than xfree86's.
OK, I'm going to close this as LATER, pending a valid reason for this stuff. Potential reasons include DRI CVS snapshot ebuilds, which require external Mesa.
*** Bug 42597 has been marked as a duplicate of this bug. ***
I have an possible idea for a reason: If someone is a developer and wants to test/use features that his gfx-card does not support (i.e. OpenGL 1.5), maybe he wants to use MESA. Not sure if this is a good reason, so i leave the bug marked as "LATER".
We don't have the resoures to support this at this time. If you'd like to write/update an ebuild and attach it here, we might be able to add that, but we don't have time to deal with it ourselves as things stand.
I really tried to modify the 3.5 ebuild to work with 6.0. I have a very huge lack of knowledge concerning ebuilds :) For the moment i will not focus on updating this ebuild since i got other things on my list. I will take a look at it if i have some spare time.
> Yeah, we haven't been supplying an external mesa because xfree86 provides its > own, and that's about the only use for mesa in portage at present. Do you have > any reason it should be in portage? XFree's copy is old and may use HW acceleration. Sometimes pure SW implementation from recent Mesa is needed. For example, Mesa provides libOSMesa for rendering into memory buffer. Also note that Mesa can be used *without* X11, but with only OSMesa or e.g. SVGAlib instead.
We're likely to start providing it once they begin providing the 3D drivers in their releases.
That's happened.
In portage.
