| 6 Jun 2024 |
 jaen | In reply to @erahhal:matrix.org
How did this option work before? Seems that it must have had access to some persistent host folder It's extra-sandbox-paths IIRC, if you want to know what to google for. Incidentally, since we're on the topic of ccache — does it need anything else other than a directory (say, programs.ccache.enable = true or something)? | 22:04:37 |
 atemu12 | Enabling it without persistence is counter-productive as ccache makes cache misses a little slower actually | 22:04:55 |
| atemu12 | Just the dir | 22:05:24 |
 erahhal | When I first tried robotnix a while back with a supported phone and OS version it worked with ccache enabled and no daemon settings | 22:05:36 |
| atemu12 | Ccache manages that don its own | 22:05:41 |
| atemu12 | Did you have a working sandbox back then? | 22:06:19 |
| erahhal | I didn't even know about the sandbox until today :) | 22:06:39 |
| erahhal | I'm still a relative novice with Nix | 22:06:57 |
| erahhal | Perhaps something changed with the lineage build or with nix since then. It was a while ago | 22:07:25 |
| erahhal | It was Lineage 18 on a OnePlus3, pretty old | 22:08:42 |
| atemu12 | You really do want ccache to work though. It can speed things up by ~2x with some tweaks. | 22:11:35 |
| atemu12 | https://github.com/Atemu/robot-config/blob/d6c4357332d626b287e6711d622bb485a4db33ee/common.nix#L16-L17 | 22:14:19 |
| erahhal | let me try restarting. It looks like the build is working btw. | 22:15:29 |
| erahhal | looking at the nix build flags and not seeing one that disables sandboxing for a particular path. | 22:21:02 |
| atemu12 | erahhal: Under --option | 22:23:05 |
| atemu12 | You should probably add this to your nixos config though | 22:23:46 |
| atemu12 | Because it needs you to be a trusted user | 22:24:10 |
| erahhal | Still confused. Looking at the nix.conf options, I don't see something that disables sandboxing for an individual path. Or are you saying to completely disable sandboxing? | 22:28:52 |
| jaen | Try this one? https://nix.dev/manual/nix/2.22/command-ref/conf-file.html#conf-sandbox-paths I've been using --extra-sandbox-paths for now so not 100% it's this, but looks like it | 22:34:55 |
| erahhal | ah, the sandbox-paths mount them into the sandbox. I was thinking the opposite, i.e. that the daemon would have access outside of the sandbox for those paths | 22:36:06 |
| erahhal | let me try that | 22:36:09 |
| erahhal | thanks | 22:36:12 |
| erahhal | Same thing in effect | 22:36:27 |
| jaen | * Try this one? https://nix.dev/manual/nix/2.22/command-ref/conf-file.html#conf-sandbox-paths I've been using --extra-sandbox-paths for now so not 100% sure it's this, but looks like it | 22:36:43 |
| erahhal | Redacted or Malformed Event | 22:52:07 |
| erahhal | Ok that worked! | 23:01:32 |
| erahhal | I'll look at cleaning up that PR. | 23:10:53 |
| erahhal | So the one repo it uses when building that is not from github is pantah-kernel. For standard lineage builds, it's using the branch android-14.0.0_r35. Currently greping through the source repos to figure out how the system determines that | 23:40:49 |
| erahhal | Also, is it possible to configure the build so that it matches a standard LineageOS build, e.g. I could install over standard lineage and not lose data? Does that involve signing the build? Or anything else? | 23:41:46 |
| erahhal | Found an answer to the first question: https://github.com/LineageOS/android/blob/lineage-21.0/default.xml#L14 | 23:47:37 |
