| 19 Feb 2026 |
 emily | FWIW: https://github.com/NixOS/nixpkgs/pull/492100 | 14:11:30 |
| emily | still need to do some work to get CI passing, and then I'll put up the draft PR for 26.11 that does the actual drop. (I also have, like, hundreds of treewide commits cleaning things up and fixing update scripts for the fallout of that, but they'll need cleaning up to be ready to send out even in draft form.) | 14:12:03 |
 Randy Eckenrode | The message suggests we will be keeping the platform definition but not building it. When do we get to delete it completely? | 14:28:49 |
| Randy Eckenrode | * | 14:29:04 |
| emily | does it imply that? I didn't intend to. I delete it in my commits that I'm going to push out | 14:30:29 |
| emily | you can --argstr system whatever you want to Nixpkgs, it just won't manage to bootstrap for most possible choices | 14:30:58 |
| emily | (do you mean the release notes? that's mostly from the copy I wrote for last release) | 14:37:45 |
| Randy Eckenrode | Yeah, the release notes. I can see someone interpreting, “we will no longer build packages for x86_64-darwin or guarantee that it can build at all,” that they can try anyway and fix what breaks on their own. | 14:40:10 |
| Randy Eckenrode | * Yeah, the release notes. I can see someone interpreting, “we will no longer build packages for x86_64-darwin or guarantee that it can build at all,” as they can try anyway and fix what breaks on their own. | 14:40:24 |
| emily | they can in their own tree :) | 14:45:55 |
| emily | I can look at adjusting the wording once I actually have things evaluating. | 14:46:21 |
| emily | you know you have a great patch stack going when squashing things into the first commits of it with Jujutsu is noticeably slow | 15:58:45 |
| emily | because it has to rebase the hundred commits after it | 15:58:54 |
| emily | Randy Eckenrode: do we have a plan for Wine, btw? I believe you said that x86 emulation on AArch64 didn't work on macOS upstream currently? | 16:01:06 |
| Randy Eckenrode | No plan at the moment. | 16:02:23 |
| Randy Eckenrode | It would be good to get Wine building on aarch64, so Linux users can use it with Fex, but Fex doesn’t work on Darwin AFAIK. | 16:03:01 |
| emily | seems possible we'll want to keep just enough around to keep that working, though I didn't do any work to achieve that in my branch | 16:03:06 |
| emily | FEX does ship a PE-format DLL for Wine's AArch64 emulation stuff | 16:03:29 |
| emily | is there a reason to expect that wouldn't work? | 16:03:36 |
| Randy Eckenrode | I wouldn’t bother. CrossOver will need to do something to deal with it eventually. | 16:03:37 |
| emily | Apple did signal that enough of Rosetta will remain that it's plausible CrossOver can continue using it, though I have no idea how that's actually going to work | 16:04:11 |
| Randy Eckenrode | My understanding is it doesn’t work on Darwin, but I haven’t dug into why. | 16:04:12 |
| Randy Eckenrode | For legacy games. CrossOver also needs to support non-game applications. | 16:04:43 |
| emily | I doubt they can make the system detect whether an app is a game or not :) | 16:05:21 |
| emily | especially inside Windows emulation | 16:05:28 |
| emily | https://github.com/FEX-Emu/FEX/blob/main/Data/nix/WineOnArm/shell.nix uh :D | 16:05:57 |
| emily | apparently FEX's WINE DLLs that they ship are literally built using Nix ^^ | 16:06:14 |
| Randy Eckenrode | If CrossOver needs frameworks that aren’t supported under future Rosetta 2, it wouldn’t work. Apple could also limit it to signed games with known team ids. | 16:30:08 |
| Randy Eckenrode | We don’t know because Apple isn’t saying anything about how they will limit it. | 16:30:40 |
| 19 May 2021 |
|  @grahamc:nixos.org set the history visibility to "world_readable". | 19:22:35 |
