| 17 Dec 2025 |
 dish [Fox/It/She] | as much as I don't like doing this, we probably want to build all the bootstrap tools into a tarball at the end of it, that way we have a single blessed bootstrap path where all platforms get a tarball and busybox and go from there, and we're not special-casing platforms that use minimal-bootstrap into a different code path. | 17:45:32 |
| dish [Fox/It/She] | Simplicity is the way to go here, after all | 17:45:38 |
 K900 | Actually kinda disagree, I think it makes sense to cross-bootstrap the other platforms | 17:46:19 |
| K900 | And then we can just have Nix handle caching | 17:46:27 |
| dish [Fox/It/She] | sounds good to me | 17:46:40 |
| dish [Fox/It/She] | as long as we have a single code path then that makes everyone's life better(even if that involves cross-building on non-minimal platforms) | 17:47:02 |
| dish [Fox/It/She] | since stdenv doesn't need more complexity | 17:47:17 |
| dish [Fox/It/She] | frankly it hurts my head sometimes lol | 17:47:22 |
| 18 Dec 2025 |
 aleksi | Can we cross-bootstrap even the darwin platforms from Linux? | 08:58:00 |
| K900 | No, Darwin needs its own bootstrap chain I think | 09:10:11 |
 emily | that would also make Darwin development a pain | 11:37:05 |
 Alex | Is it not already? | 12:05:38 |
 Randy Eckenrode | Maybe once Darwin is switched to LLVM/LLD bintools. | 12:37:14 |
| Randy Eckenrode | But it would still be painful without some way to emulate the Linux part. | 12:37:36 |
