| 6 Nov 2025 |
 ma27 | if you use strings of hydra jobset names instead of derivations in the constituents list, it does though. | 16:27:59 |
 vcunat | Speaking of its performance, I'm still horrified that building that job implies copying closures of all constituents to a builders, which in our case can get really big. The only luck is that we have very few builders, so usually most of it is there already. | 16:29:42 |
| vcunat | * Speaking of its performance, I'm still horrified that building that job implies copying closures of all constituents to a builders, which in our case can get really big. The only luck is that we have very few (but powerful) builders for linux, so usually most of it is there already. | 16:29:55 |
| vcunat | * Speaking of its performance, I'm still horrified that building that job implies copying closures of all constituents to a builders, which in our case can get really big. The only luck is that we have very few (but powerful) builders for *-linux, so usually most of it is there already. | 16:29:59 |
| vcunat | * Speaking of its performance, I'm still horrified that building that job implies copying closures of all constituents to a builder, which in our case can get really big. The only luck is that we have very few (but powerful) builders for *-linux, so usually most of it is there already. | 16:30:15 |
| 9 Nov 2025 |
|  ghpzin (moved to @ghpzin:envs.net) changed their display name from ghpzin to ghpzin (moved to @ghpzin:envs.net). | 15:03:54 |
| 12 Nov 2025 |
|  Inayet changed their display name from inayet to Inayet. | 12:38:09 |
|  André Lima joined the room. | 19:58:30 |
| 13 Nov 2025 |
|  @wolfgangwalther:matrix.org left the room. | 08:31:18 |
|  eveeifyeve joined the room. | 15:18:44 |
| 16 Nov 2025 |
| eveeifyeve | Hey Hydra team, do you know the best way we can build tarballs for cgywin, we are successfully building it with GHA? Because that might be something that I want to work on for windows. | 17:20:16 |
 K900 | Tarballs of what? | 17:20:57 |
| eveeifyeve | Cygwin builds of nix. | 17:21:25 |
| K900 | And why do we need those on Hydra? | 17:21:43 |
| eveeifyeve | It's building fine on GHA although we are running into a limit of the hours on github. | 17:22:16 |
|  Corngood joined the room. | 17:22:29 |
| K900 | Who is "we"? | 17:23:00 |
| eveeifyeve | Both me and corngood. | 17:23:17 |
| eveeifyeve | https://github.com/corngood/nixpkgs/actions/workflows/cygwin.yml | 17:23:19 |
| Corngood | The tarballs will be for bootstrapping, like on other platforms. The real problem at the moment is not having a cache. | 17:25:34 |
| K900 | I don't have a nixpkgs core hat anymore | 17:26:19 |
| K900 | But you'll need a really good argument | 17:26:29 |
| K900 | To convince me that cygwin is worth supporting | 17:26:34 |
| Corngood | Supporting just means having windows builders, right? Has that been discussed for any other purpose? | 17:27:46 |
| K900 | Supporting means code in nixpkgs | 17:28:28 |
| K900 | And Hydra time | 17:28:30 |
| K900 | But primarily the former | 17:28:33 |
 dramforever | supporting means going up https://github.com/NixOS/rfcs/blob/master/rfcs/0046-platform-support-tiers.md | 17:28:46 |
| Corngood | Well we already have cross builds in nixpkgs. The rest is progressing. | 17:29:46 |
| dramforever | If you need a builder, namespace.so provides runners for nix-community projects https://nix-community.org/namespace-actions/ | 17:29:51 |
