Please see
https://bugs.gentoo.org/show_bug.cgi?id=612454 for context.
Chromium builds the following libraries (among others): libEGL.so, libGLESv2.so, libosmesa.so . These are usually provided by system mesa package, and so packagers are wondering what's different about our copies.
FWIW, the package seemed to work just fine with these files removed, although I didn't test more sophisticated WebGL demos for example.
Some questions for experts (feel free to redirect me to appropriate ML):
1. Are these files supposed to be installed on the system with the browser? "dpkg-query -L google-chrome-stable | grep \\.so" only shows some Widevine shared objects for me. Maybe we should suggest packagers not to ship the GL .so files?
1a. In case the GL .so files should not be installed, why are they built as part of the build process? How can I verify functionality which might depend on them is working correctly?
2. What does the browser expect from the system wrt GL? I found that e.g. on Gentoo osmesa doesn't seem to be the default, but can be depended on. Currently Gentoo Chromium package doesn't do that though.
3. Do you have recommendations for testing GL-related functionality? I used to check obvious things such as about:gpu, but frequently it shows to me most of the functionality is disabled or software-only.
3a. Are there hardware configurations recommended to test this?
3b. May running inside a chroot affect about:gpu results? My tests suggest that to be the case (I could provide you specific results upon request).
Paweł