| 2 Jan 2025 |
 atemu12 | You first gotta figure out how to do it with AOSP and then just inject that declaratively via robotnix | 20:28:31 |
 countoren | yes that will be one way, but if you would like to add custom configurations/services we might want something like robotnix.rc that will be written from the expression directly | 20:30:13 |
| atemu12 | Sure, feel free | 20:30:34 |
| atemu12 | to build that | 20:30:39 |
| countoren | I might go to this direction | 20:30:59 |
| atemu12 | There's precedent for stuff like this in e.g. the webviews | 20:31:01 |
| countoren | not 100% sure | 20:31:05 |
| atemu12 | Or system APK handling | 20:31:10 |
| atemu12 | I'd recommend you try to do it via a Magisk overlay first though for quicker iteration | 20:31:35 |
| countoren | the cool thing about that you will be able to cross compile you own services if you want and just run them from robotnix.rc | 20:32:21 |
 oak 🏳️🌈♥️ | Usually with Android it's not that easy, or I mean you need to provide build scripts on how to build the thing as part of the Android tree | 20:33:29 |
| countoren | at work for me it was as straightforward as that | 20:34:13 |
| countoren | and I am able to access wifi, serial from the service without any other config | 20:34:58 |
| countoren | using crossPkgs, pkgsStatic | 20:36:03 |
| oak 🏳️🌈♥️ | Properly packaging a native low-level Linux-daemon for Android is a process which involves multiple kinds of steps, for example you need to provide the necessary SELinux policy in addition to other things | 20:36:26 |
| countoren | yes we had to do that too | 20:37:13 |
| oak 🏳️🌈♥️ | Builds done with pkgsStatic won't use the Android's bionic libc, but instead something that is provided by nixpkgs, statically built into the binary | 20:37:52 |
| atemu12 | nix-daemon when? | 20:38:23 |
| countoren | yep | 20:38:51 |
| oak 🏳️🌈♥️ | For quick hacking that is probably fine, but if you want to properly package software for Android System then it should be built as part of the Android tree | 20:39:10 |
| oak 🏳️🌈♥️ | For example if you are actually aiming to productize something officially | 20:39:21 |
| atemu12 | I mean, we'd just use the nixpkgs ones and add the selinux rule to allow the Nix store just like on Fedora | 20:39:45 |
| atemu12 | Or perhaps add a permission for apps to use it | 20:40:02 |
| countoren | it will be the actual differences | 20:40:27 |
| countoren | * what will be the actual differences | 20:40:37 |
| countoren | * what will be the actual differences? | 20:40:47 |
| atemu12 | I think we're squarely in the "hacking stuff" field rather than anything close to "productise" or "officially" | 20:41:00 |
| atemu12 | I think they mean to build whatever software you want to run as a daemon against the AOSP sources such that it's like the other daemons in Android | 20:41:56 |
| atemu12 | When in Rome, do as the Romans do | 20:42:05 |
| oak 🏳️🌈♥️ | Build done inside the Android tree will use the same compilers and other same tooling that is used to build the rest of the system | 20:42:33 |
