| 6 Jun 2024 |
 erahhal | It was Lineage 18 on a OnePlus3, pretty old | 22:08:42 |
 Atemu | You really do want ccache to work though. It can speed things up by ~2x with some tweaks. | 22:11:35 |
| Atemu | 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 |
| Atemu | erahhal: Under --option | 22:23:05 |
| Atemu | You should probably add this to your nixos config though | 22:23:46 |
| Atemu | 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 |
| 7 Jun 2024 |
| erahhal | One oddity with ccache is that it never goes much above 1.6G. it will go larger temporarily, then go back down to 1.6G. ccache.conf is present and indeed set to 100G | 02:59:12 |
| erahhal | * One oddity with ccache is that it never goes much above 1.58G. it will go larger temporarily, then go back down to 1.58G. ccache.conf is present and indeed set to 100G | 03:09:37 |
| erahhal | Maybe the conf isn't getting picked up | 03:20:46 |
 @samueldr:matrix.org | or the cache doesn't need more space because it's not being exercised? | 03:54:40 |
| @samueldr:matrix.org | if you're rebuilding the same "moral" thing, I would expect the cache won't change size much | 03:55:06 |
| @samueldr:matrix.org | (it's just a guess) | 04:03:19 |
| erahhal | Yeah that's totally possible. | 04:33:44 |
| Atemu | In reply to @erahhal:matrix.org
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? That should be the default. If it's not, that's a bug | 08:27:18 |
| Atemu | Though note that your signing keys won't match | 08:28:50 |
