Open dandongus opened 1 year ago
I'd assume most of the ungoogled-chromium patches are in non-OS specific parts, while the chromium-legacy patches are mostly in the mac platform specific portions. The former could likely be applied on top of the latter without too many merge conflicts to sort through, but it would increase the maintenance burden (and especially double the number of builds). It also makes bug reports trickier to triage since now there's two possible upstream sources that would need to be combed through. I don't know if bluebox has enough time to support such a setup...
If you are particularly interested in ungoogled-chromium patches though, you could try building yourself.
The thing with ungoogled-chromium is that by removing the questionable stuff / tracking and whatnot the browser is even faster and less resource intensive. This could be a big advantage on older OSX systems.
Thank you for all the ongoing efforts.
How much work would it be to 'combine' these two projects? If it's feasible, is it something you'd ever consider doing and providing as a separate version or branch, or completely out of the question?