| 23 Dec 2024 |
 oak 🏳️🌈♥️ | It is possible to fix that specific issue but then there are other issues with the Chromium Webview builder later in the process as well | 13:35:30 |
| oak 🏳️🌈♥️ | Mainly I found out last time I was looking at it, that during past few years the build process of Chromium has changed so that it required their own distribution of Python to be able to fetch all the source code, and the "flattening" of the tree has been broken | 13:41:20 |
| oak 🏳️🌈♥️ | Then I had this idea of leveraging the stuff that already exists for building Chromium for NixOS in nixpkgs but hadn't had enough time to look on that, by default it only builds few different variants for Linux | 13:42:01 |
 atemu12 | Honestly getting a working prebuilt webview such as mulch is much higher priority | 14:09:32 |
| atemu12 | Ideally it'd be the mulch overlay so that it's use upgradable at runtime | 14:10:11 |
|  erahhal set a profile picture. | 18:32:01 |
| oak 🏳️🌈♥️ | Yeah, I think we could have both, IIRC there's already a mechanism which you can optionally use to select one of the webviews. I don't think adding prebuilt webview should anyway be that big task | 18:54:08 |
| atemu12 | Yup, just needs to be done | 18:54:50 |
| oak 🏳️🌈♥️ | Maybe I could also have a look on adding that, but I don't have my second test phone with me now during christmast time | 18:54:53 |
| atemu12 | We should really get the emulator to work again too | 18:55:18 |
| oak 🏳️🌈♥️ | How does it work if you build LineageOS "normally" (I mean without Robotnix)? Does it have the prebuilt webview already added in repo manifest? | 18:55:45 |
| atemu12 | It does but I think robotnix was interacting with it poorly | 18:56:07 |
| atemu12 | It'd always be disabled IIRC | 18:56:15 |
| atemu12 | So you had to use the robotnix-provided webview | 18:56:28 |
| atemu12 | Or none at all | 18:56:32 |
| atemu12 | I'm also not sure the LOS webview is up to date | 18:56:46 |
| oak 🏳️🌈♥️ | Yeah actually now I recall, when I was updating those flavour repo.json files, I noticed it does fetch prebuilt webview, and I had some problems with it. (To fix the problems I had to remove the repo.json and do completely clean run of the update script.) | 18:57:44 |
| 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 |
