> Tell me about it! I've been secretly maintaining a Chromium branch over > at https://github.com/mbakke/guix/commits/chromium . It's frequently > rebased.
Looks awesome! > One thing that worries me about Inox is that version 53 is very old and > likely contains known vulnerabilities. Do you know if they backport > fixes? If not, I think we should try to stick with upstream Chromium. This is due to me not having worked on it for a while. Inox are just a couple of patches and default configure flags, but it's still chromium. I'm not too concerned with inox, but *whisper* I got the impression that there where FSDG issues with chromium. By applying a bunch of patches and calling it inox instead of chromium, I think it could be considered a "good faith effort", and the problem avoided until someone complains. Another interesting collection of chromium patches would be: https://github.com/Eloston/ungoogled-chromium > Also, Chromium 54+ have abandoned the "gyp" build system completely in > favor of the "gn" build system. With it, many build flags don't work > properly yet. See the FIXMEs in the HEAD of the above branch :-) Good to know, thanks for the heads up! > Anyway, great work so far, hopefully we can join efforts and get this in > somehow. I'm not happy with the current build, the 3rd party stuff > should be removed in a source snippet, and some sites tend to just > "hang" infrequently, likely from one of the patches (IPv6 probe?). Sounds good! We should definitely use your package as a base...
