| 22 Sep 2024 |
 cafkafk | How invasive would it be to setup a host as an darwin builder, if it's not expected to be its only/primary use? | 09:44:37 |
| cafkafk | Like, does ofborg just use a list of remote builders, or do the hosts actually need to be dedicated | 09:45:21 |
| cafkafk | * Like, does ofborg just use a list of e.g. remote builders, or do the hosts actually need to be dedicated solely to ofborg | 09:45:37 |
 7c6f434c | It still doesn't use cachix uploads, right? | 09:47:27 |
| 7c6f434c | If so, it's basically add a bunch of identifiers into the config, build a package, run the binary in it with that config | 09:48:18 |
| 7c6f434c | During a build it might consume all the CPU you let it (not sure how you limit that on macOS) | 09:49:00 |
| 7c6f434c | But like any heavy Nix build | 09:49:11 |
| 7c6f434c | The system is pretty OK with intermittent availability | 09:49:54 |
| cafkafk | Also there is the issue of limited sandboxing on darwin I guess | 09:50:20 |
| 7c6f434c | Back in the day, the move to internally controlled builders was partially motivated by the complexity of tracking ofBorg versions across the fleet | 09:50:57 |
| 7c6f434c | If the things are more stable today, this issue might no longer be relevant | 09:51:14 |
| 7c6f434c | Darwin sandboxing is an issue, probably | 09:51:26 |
