On Tue, Feb 7, 2017 at 8:47 AM, Simon Farnsworth <simon@xxxxxxxxxxxx> wrote: > >> On 6 Feb 2017, at 22:01, Jan Pokorný <jpokorny@xxxxxxxxxx> wrote: >> >> On 06/02/17 15:13 -0500, Christian Schaller wrote: >>> There has been a lot of discussions for the last few years about glvnd on >>> the mesa-devel list and at XDC. This is not Fedora specific technology, but >>> a change in how Mesa will work everywhere and thus there has not been a lot >>> of discussions about it here on Fedora-devel. But that is true for most stuff, >>> we do not discuss major new kernel features here that much either as one example. >> >> I don't think that's a fair point. If there was an artificial >> intermediate level put in front of libc that would only be to >> solve issues with some hardware component, and it would be forcibly >> implanted into Fedora unnecessarily for all audience, then it would >> be comparable. >> >> But even then, I doubt it would happen without questioning such >> aspects. >> >> Forcing glvnd for all is Fedora specific, as far as I can tell. >> > Note, however, that glvnd is replacing an existing Mesa indirection layer (used to allow one Mesa build to link in the appropriate OpenGL libraries for AMD Radeon, Intel iGPUs, Noveau etc at run time) with an indirection layer that can also link in other drivers for OpenGL, not just Mesa ones. > > In other words, this isn't putting an artificial intermediate layer in front of a library - it's replacing one intermediate layer with another that happens to allow for more back end implementations than the old one did. > btw, at the risk of venturing off topic, a side note that no one has brought up: libglvnd also introduces a new gl ABI.. in addition to the compat libGL.so which for historical reasons drags in GLX and X dependencies, also provides libOpenGL and a separate libGLX (so you can use, for example, libOpenGL + libEGL with no X11 dependencies). That is a pretty nice, and long overdue, cleanup, IMHO. BR, -R _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
