[yocto] [PATCHv4 6/8] mesa-dri.bbappend: avoid conflict with emgd-driver-bin

[Burton, Ross]

On 12 October 2012 00:31,  <nitin.a.kamble at intel.com> wrote:
> Extend the mesa-dri recipe from oecore to avoid conflict with
> files generated by emgd-driver-bin recipe.

The commit message should also say what the high level changes were,
in this case

> +# To avoid conflict disable egl, gles1, gles2 from meta-dri if the BSP image
> +# is bundling the emgd driver.

I'm not entirely keen on this level of deep hackery, it looks very
fragile.   Is there any difference in the headers installed by emgd
and mesa?  An alternative would be to consider mesa a more canonical
source of GL headers for the build, and change EMGD to not install
anything to staging.   This would mean that emgd wouldn't build-time
provide any virtual/libgl packages, just runtime provides so that the
image can be built using EMGD and Mesa's libgl.

FYI, In ross/xorg I've started re-arranging the packaging of mesa, so
that the packages are called libgl-mesa and RPROVIDE libgl.  I plan to
make the same changes to EMGD once I have the shlib resolution sorted.

Ross