| 28 Sep 2025 |
 Lun | If I import release-rocm's jobs into release do I need to make sure all the names end up unique or it'll break? So if release-rocm.nix is making an "openmpi" job that needs to be something else to be valid to add in release.nix and not conflict with the default openmpi | 15:29:48 |
| Lun | https://github.com/LunNova/nixpkgs/blob/push-kuknstozqsvo/pkgs/top-level/release-rocm.nix is what I have as an attempt at a release-rocm.nix but I'm not clear on what importing it in the main release properly would look like | 15:42:20 |
 Vladimír Čunát | I thought we'd nest it all under some name like rocmPackages to avoid name collisions. | 15:48:48 |
| Vladimír Čunát | * I thought we'd nest it all under some name like pkgsRocm to avoid name collisions. | 15:49:45 |
| Vladimír Čunát | pkgsRocm exists but doesn't generate jobs on Hydra. So ideally we'd reuse the attribute paths to reduce confusion? (but only put the chosen packages into it and not everything) | 15:52:43 |
 SomeoneSerge (matrix works sometimes) | Was the separate-jobset option already dismissed? | 16:59:25 |
| Vladimír Čunát | I'm not against a separate jobset. But I haven't heard any advantage to gain from the separation. | 17:09:41 |
