| 2 Jan 2025 |
 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 |
