| 17 Mar 2024 |
 infinisil | Very related: https://github.com/NixOS/nixpkgs/pull/252057 | 14:23:41 |
 Robert Hensing (roberth) | Yeah, might as well record which channel version it's based on - keep another data package in sync | 14:24:37 |
| Robert Hensing (roberth) | (not exactly the same thing, but related indeed) | 14:26:33 |
| infinisil | Alternatively, consider a more powerful idea of having a meta-Nixpkgs repository, which contains all historical versions of Nixpkgs that were built by Hydra, with all their metadata. This could include things like whether builds succeeded, which versions are available in which channel, what is the latest release, etc. | 14:27:17 |
| infinisil | Robert Hensing (roberth): This reminds me of the release notes problem you're having with Nix, where some release notes are only available in release branches, never getting to master from where the manual is rendered | 14:28:52 |
| infinisil | I can see such meta repositories also solving that problem | 14:30:07 |
| infinisil | Oh and it should be purely additive, no data should ever be removed from such repos | 14:30:21 |
| infinisil | Which means they don't even need to be repos really, though that might be easiest | 14:30:34 |
| infinisil | And at that point we're back at maybe it should just be a channel! | 14:30:48 |
|  willbush left the room. | 14:48:32 |
| willbush joined the room. | 14:48:50 |
| willbush left the room. | 14:49:53 |
| willbush joined the room. | 14:50:26 |
 tomberek | Sounds very much like the catalogs we had been working on. Doing them all is likely too much, but we can make a 1-1 relationship as a starting point, before doing all of history at once. | 14:52:51 |
| tomberek | Do you mean something close to: https://github.com/on-nix/pkgs ? | 14:54:11 |
| willbush | infinisil: is there a way to manually run by-name tests? for example, I was trying cargo run -- --base ./tests/empty-base ./tests/aliases | 14:57:20 |
| infinisil | willbush: Ahh there isn't, I usually do cargo test to run them all | 14:58:55 |
| infinisil | That's actually something I'd love to have improved: Currently when I update error messages, I manually update the error messages in the tests. I'd rather just be able to regenerate them | 14:59:34 |
| infinisil | https://crates.io/crates/insta could do that I believe | 15:00:25 |
| infinisil | (well and running individual tests, kind of related) | 15:00:53 |
| willbush | Ok no problem! I was just wanted to go through each test to make sure I understand why they should pass or fail. However, I can cargo test -- --nocapture and throw some println statements in the cargo tests. | 15:01:13 |
| infinisil | Oh neat, didn't know about that! | 15:07:48 |
| infinisil | Oh neat, yes! | 15:10:06 |
| tomberek | From playing with this idea before, I really recommend having a separation between the kinds of pure/impure, eval/build, snapshots/historical. Mixing them leads to problems each time. | 15:22:55 |
 Growpotkin | I'd echo what Tom said. | 15:42:29 |
| Growpotkin | * I'll echo what Tom said. | 15:42:59 |
| Robert Hensing (roberth) | As long as Nixpkgs and NixOS don't start to depend on such a repo in a way that makes using branches and forks harder, why not. | 18:09:40 |
 @jade_:matrix.org | In reply to @infinisil:matrix.org
Alternatively, consider a more powerful idea of having a meta-Nixpkgs repository, which contains all historical versions of Nixpkgs that were built by Hydra, with all their metadata. This could include things like whether builds succeeded, which versions are available in which channel, what is the latest release, etc. yes yes yes please do it with clever merge commits on a branch | 18:28:40 |
 SomeoneSerge (back on matrix) | I presume there would've already been some discussions on this matter and somebody in this room would know where to redirect me: https://github.com/NixOS/nixpkgs/issues/296544 | 18:34:23 |
 Qyriad | In reply to @jade_:matrix.org
yes yes yes please do it with clever merge commits on a branch that over git notes or something? | 18:35:04 |
