| 23 Dec 2024 |
 oak 🏳️🌈♥️ | The problem is that if you build without any webview at all, if you want to use GApps, you can't log into your google account if you don't have at least some kind of webview | 18:59:00 |
| oak 🏳️🌈♥️ | I was wondering why does it have to fetch the prebuilt webview if it's not going to be used anyway, but I guess the reason is that it's in the LineageOS's repo manifest | 19:00:33 |
| oak 🏳️🌈♥️ | https://github.com/LineageOS/android_external_chromium-webview_prebuilt_arm64 Well it's not that old | 19:04:24 |
| oak 🏳️🌈♥️ | I'm curious what was the build issue though | 19:04:38 |
| oak 🏳️🌈♥️ | https://android.googlesource.com/platform/external/chromium-webview/ This should be the place for official releases of webview from Chromium project, with these Google projects I always wonder what is the correct branch to use though, maybe main? | 19:12:48 |
 atemu12 | https://divestos.org/pages/news#end | 22:11:08 |
| atemu12 | Well darn, so much for using Mulch... | 22:11:21 |
 magic_rb | Huh that was abrupt holy shit | 22:22:49 |
| 24 Dec 2024 |
| oak 🏳️🌈♥️ | I wonder what are the important things to take into account when packaging those prebuilt apks. Mainly first question that comes to mind is that do the signatures need to be changed or spoofed? | 22:17:24 |
| oak 🏳️🌈♥️ | * I wonder what are the important things to take into account when packaging those prebuilt apks. Mainly first question that comes to mind is do the signatures need to be changed or spoofed? | 22:17:39 |
| atemu12 | Depends on whether you want to sign them with your key or keep the upstream key | 22:18:00 |
| atemu12 | There's valid reasons for both | 22:18:42 |
| atemu12 | You'd want to sign it with your key unless you want to be able to update it independently of the ROM | 22:19:23 |
