| 20 Mar 2024 |
 Philip Taron (UTC-8) | Yeah, I think that's covered by the move to a separate repo. | 23:03:26 |
 infinisil | Oh it's here: https://github.com/NixOS/nixpkgs/tree/master/pkgs/test/nixpkgs-check-by-name/scripts#update-pinned-toolsh | 23:03:37 |
| infinisil | See the "Why not just build the tooling right from the PRs Nixpkgs version?" part | 23:03:46 |
| Philip Taron (UTC-8) | OK, those are pretty compelling. | 23:04:21 |
| infinisil | Oh what would work is to also pin the Nixpkgs version for the tool | 23:05:14 |
| infinisil | So it's (import pinnedNixpkgs {}).callPackage instead of pkgs.callPackage | 23:05:38 |
| infinisil | Well you'd still need to have it be cached somewhere though.. | 23:06:19 |
| Philip Taron (UTC-8) | We can do a three-step release process.
- Validate in the check-by-name repo; make a release.
- Update nixpkgs repo with the new release; wait for it to make its way into the cache.
- Update the pin to the nixpkgs-built version.
That's lame and laborious, but it's all-cache-no-brakes.
| 23:08:20 |
| infinisil | Part of the reason I wanted to move it to a separate repo was to have a separate Hydra jobset, such that we didn't need to wait for channel updates 😅 | 23:09:19 |
| infinisil | Using GitHub releases as a cache (I guess it's not a cache then really, just a build artifacts storage) sounds decent | 23:10:51 |
| infinisil | It should be possible with nix-store --export without too much trouble | 23:11:21 |
