mdedonno1337
commented
3 years ago I'm working at the moment on my gitlab actions to do that. From a security point of view, I think that the compilation shall be done here directly to provide the binaries as github actefacts.
I'm working on my side to understand how the super-project and submodules is working, and let you know.
I'm ok, once working on my side, to make a PR and maintaine it.
Edit: What I have working at the moment:
- Compilation of ungoogled-chromium (with
./docker-build.sh) - Conversion to an AppImage (for the version 87.0.4280.141)
What is not working:
- Same compilation process for the versions 88 (88.0.4324.104-1) and up: one patch does not apply. I dont know at the moment if my process is breaking something with the compilation of the submodule OR if the submodule can not be compiled as-is. I did not, at the moment, tried to edit theh patch manually / understand why can not be patched:
INFO: * Applying gpu-timeout.patch (9/23)
patching file gpu/ipc/service/gpu_watchdog_thread.cc
Hunk #1 FAILED at 44.
1 out of 1 hunk FAILED -- saving rejects to file gpu/ipc/service/gpu_watchdog_thread.cc.rejWorking on that part at the moment.
Eloston
Question: Can we automate updates to this repo whenever ungoogled-chromium updates?
Since the amount of changes (patches, build flags, etc.) is relatively small, I suspect we could write a simple GitHub Actions workflow that tries to refresh all the changes. If it fails part-way, maybe we could have it draft a PR that we can continue working on.
It might help keep this repo up-to-date, because I think most of the devs here don't update this repo because it's more work than it's worth (compared to other platform repos).