On 2/22/24 16:50, Charles Samuels wrote:
On Thursday, February 22, 2024 9:52:03 A.M. PST Andres Salomon wrote:Swiftshader is manually disabled in Debian's chromium package. It's one of those legacy patches that I've long meant to look at (and remove if conditions allow it), but I haven't gotten to yet: https://salsa.debian.org/chromium-team/chromium/-/commit/84db0501b0d6cb055fe 9f22057cd129fdefac710It wasn't documented *why* swiftshader was disabled. Maybe related to non-DFSG third party libs (see https://bugs.debian.org/909156)? In order to reenable it, I need to poke around and see if I can figure out why it was disabled in the first place.I looked at all of swiftshader's dependencies' licenses: SPIRV: Apache astc-encoder: Apache benchmark: Apache boost: Boost license (already part of Debian) cppdap: Apache glslang: 3-BSD, 2-BSD, MIT, Apache, GPL3, an NVIDIA license, which seems to be similar to the MIT/BSD licenses, Khronos License, already part of debian. glslang is already part of Debian json: MIT libbacktrace: BSD llvm: llvm is already part of Debian llvm-subzero: same license as LLVM marl: Apache Let me know if there is any way I can help!
Thanks for checking into the licenses! The other thing to look into is whether there's any compiled stuff included in the swiftshader directory. Not just actual binaries (which at least debian/scripts/check-upstream should catch), but also .js and similar files that have been run through things like minify. With that out of the way, I'd be comfortable re-enabling swiftshader.
OpenPGP_0x645D0247C36E7637.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
