Looking for other ports using mesa and having a "uses pledge/unveil" comment in the port Makefile:
- emulators/mgba and graphics/arcan use mesa and either pledge or pledge+unveil in some way. I don't use them but they could do with a quick check at some point to make sure they don't need tweaks (not critical packages so no big need to do that before committing the change to mesa). - mupdf uses pledge in some binaries, but IIRC only mupdf-gl uses mesa and that's the one which _doesn't_ use pledge. No problems seen there. - I'm not 100% sure of the situation with qtwebengine, it has patches adding the sandbox code from chromium (looking at the files in /etc/chromium) but it's unclear whether it's actually used (or even compiled). Testing a couple of ports depending on the qtwebengine library, otter-browser doesn't complain with the mesa disk cache enabled. qutebrowser is broken for me anyway but that's unrelated to the diff. So I don't _think_ we need to worry about that. > > Index: lib/mesa/src/util/disk_cache.c > > =================================================================== > > RCS file: /cvs/xenocara/lib/mesa/src/util/disk_cache.c,v > > retrieving revision 1.13 > > diff -u -p -r1.13 disk_cache.c > > --- lib/mesa/src/util/disk_cache.c 28 Jan 2023 08:56:53 -0000 1.13 > > +++ lib/mesa/src/util/disk_cache.c 20 Feb 2023 12:42:45 -0000 > > @@ -80,11 +80,6 @@ disk_cache_create(const char *gpu_name, > > uint8_t cache_version = CACHE_VERSION; > > size_t cv_size = sizeof(cache_version); > > > > -#ifdef __OpenBSD__ > > - /* default to no disk shader cache to avoid pledge violations in > > chromium */ > > - return NULL; > > -#endif > > - > > if (!disk_cache_enabled()) > > return NULL; > > > >