| 21 Apr 2025 |
 Randy Eckenrode | Darwin bootstrap gets a fully functional Python in stage 1. | 14:52:34 |
| Randy Eckenrode | Redacted or Malformed Event | 14:54:36 |
| Randy Eckenrode | * Though having Python pulled into the stdenv is going to add it to the stdenv closure size. Darwin is already huge, so what’s another however many tens or hundreds of MiB. I don’t know about Linux. | 14:54:42 |
| Randy Eckenrode | Not sure why this should be in the bootstrap tools. Can’t it be built in stage 1? | 14:57:12 |
 Tristan Ross | Any objections to documenting platform tier support? | 21:45:32 |
| Tristan Ross | If not, we should discuss what the tiers look like and what each platform fits into. | 21:46:51 |
 emily | it's already documented | 21:51:46 |
| Tristan Ross | Wait, where? | 21:56:08 |
| emily | Nixpkgs manual | 21:56:20 |
| emily | first section, https://nixos.org/manual/nixpkgs/stable/#chap-platform-support | 21:56:35 |
| Tristan Ross | Oh, that's just a list of commonly supported platforms | 21:57:26 |
| Tristan Ross | Not a platform support tier list | 21:57:38 |
| emily | it links to the platform tier list RFC | 21:59:50 |
| emily | which was approved but failed to make complete contact with reality | 21:59:59 |
| emily | which is something like x86_64-linux Tier 1, aarch64-linux Tier 1.5, aarch64-darwin Tier 2, x86_64-darwin Tier 2.5, i686-linux Tier 3, everything else tier nothing | 22:00:48 |
| emily | RFCs are immutable so the appendix will never be updated, but in principle we have accepted the tiers themselves | 22:01:15 |
| emily | and they have quite detailed descriptions | 22:01:21 |
| emily | in practice the biggest tier distinction is just "used on NixOS infra" vs. "not used on NixOS infra" | 22:01:54 |
| emily | there are x86_64-linux, aarch64-linux, and aarch64-darwin machines in the infra so there's no choice but to keep those platforms in good shape. x86_64-darwin comes along for the ride on aarch64-darwin for the most part | 22:02:33 |
| emily | and a subset of i686-linux is required to build e.g. NixOS tests at present, so that is also kept in working order | 22:02:47 |
| emily | everything else is pretty much if it breaks you can keep both pieces | 22:02:53 |
| Tristan Ross | Gotcha, I was thinking it'd be easier if it were in the manual. It'd be mutable then. | 22:10:01 |
| emily | well, it basically is, they're just described more vaguely :) | 22:12:13 |
| emily | but yes if we want to assign actual numbers to the platforms then the manual would be the place | 22:12:27 |
| emily | the .5s sort of make it awkward to describe reality in more precise terms than is already there though | 22:12:42 |
| emily | probably Tier 1 x86_64-linux, Tier 2 aarch64-linux aarch64-darwin x86_64-darwin would be adequate | 22:14:04 |
| emily | x86_64-darwin is sort of tier 3 in practice but "No channel-blocking jobs on Hydra." isn't true | 22:14:30 |
| Tristan Ross | I'd say aarch64-linux is tier 1 by now lol | 22:23:29 |
| Randy Eckenrode | When it comes down to it, aarch64-linux is not going to be allowed to block like x86_64-linux is. | 22:28:47 |
| emily | yeah it definitely does not meet the criteria outlined for tier 1, but it is "tier 1.5"-ish | 22:30:27 |
