| 26 Nov 2024 |
 @jack:unredacted.org | Yes, maybe unpack_bootimg.py isn't prepared to handle it, so it just considers whatever is in the supposed kernel position on the file.
| 21:20:19 |
| 27 Nov 2024 |
 oak 🏳️🌈♥️ | I got a little forward by creating the FHS env, but I still can't completely run the mk-vendor-file.py for new Chromium version, now I get same errors I think it tries to pull some Google internal stuff they use for building ChromeOS and Chrome | 20:40:12 |
| 26 Nov 2024 |
| @jack:unredacted.org | Apparently there is some tools I can build to handle pvmfw stuff: m pvmfw-tool pvmfw_bin
| 21:23:26 |
| 27 Nov 2024 |
| oak 🏳️🌈♥️ | * I got a little forward by creating the FHS env, but I still can't completely run the mk-vendor-file.py for new Chromium version, now I get some errors I think it tries to pull some Google internal stuff they use for building ChromeOS and Chrome | 20:40:18 |
| 26 Nov 2024 |
| @jack:unredacted.org | * Apparently there are some tools I can build to handle pvmfw stuff: m pvmfw-tool pvmfw_bin
| 21:23:37 |
| 28 Nov 2024 |
| oak 🏳️🌈♥️ | Actually it looks like there could be some useful stuff in how nixpkgs packages chromium | 03:04:42 |
| 27 Nov 2024 |
| @jack:unredacted.org removed their profile picture. | 16:57:53 |
| @jack:unredacted.org removed their display name jack. | 16:57:54 |
| @jack:unredacted.org left the room. | 16:57:55 |
| 28 Nov 2024 |
 Atemu | Ideally we'd have a little pkgs.chromium.override { withAndroid = true; withWebview = true; } and it'd spit out an APK | 11:23:36 |
| Atemu | You could ask the upstream maintainers whether they'd accept you building in support for that | 11:24:05 |
| Atemu | (Upstream as in Nixpkgs upstream.) | 11:24:16 |
