| 8 Mar 2024 |
 @jade_:matrix.org | yeah | 21:11:31 |
| @jade_:matrix.org | I think we need a better issue search tool | 21:11:39 |
 infinisil | We could maybe add automatic labels based on whether builders, packages, or both are changed | 21:12:25 |
| @jade_:matrix.org | that would help for pr filtering yes | 21:12:39 |
| infinisil | It's hard to untangle this via files, but pkgs/by-name will help here | 21:12:48 |
| @jade_:matrix.org | but for "does it touch this attribute", there is no way to find prs lol | 21:12:50 |
| infinisil | Oh yeah, I wish github had a "search PRs by touched files" feature! | 21:13:18 |
| @jade_:matrix.org | In reply to @infinisil:matrix.org
It's hard to untangle this via files, but pkgs/by-name will help here i have a galaxy brained idea which is to associate the file of a package from the meta.location with the attr name, then collect a db table of pr files touched so i can search prs by attr path | 21:13:45 |
| @jade_:matrix.org | https://pad.lassul.us/opendata-projects# wrote some of this in here | 21:14:11 |
| infinisil | jade_: Nice! | 21:15:40 |
| infinisil | Generally I think more post-Nixpkgs processing would be really nice | 21:15:54 |
| @jade_:matrix.org | yeah | 21:15:59 |
| infinisil | programs.sqlite is an example, and it's really valuable | 21:16:04 |
| infinisil | Here's a smallish project: Replace programs.sqlite with nix-index | 21:16:29 |
| infinisil | Would deprecate https://github.com/Mic92/nix-index-database and give everybody a nix-index database by default | 21:16:50 |
| infinisil | Well, as long as you fetch channels and not git branches | 21:17:00 |
| @jade_:matrix.org | hm. channels have been killed, but we could make a hydra job for the nix-index of the current channel version.... or something? | 21:17:11 |
| @jade_:matrix.org | well | 21:17:14 |
| @jade_:matrix.org | flakes have killed channels | 21:17:18 |
| @jade_:matrix.org | whether that was actually advisable or not is another question hehehe | 21:17:25 |
| infinisil | They only killed nix-channel! | 21:17:28 |
| infinisil | Channels are still very much needed and alive | 21:17:36 |
| infinisil | Well not that much actually | 21:18:04 |
| @jade_:matrix.org | (nix-channel and the idea of mutable channels is like. genuinely Bad, but it would be nice if we could have postprocessed versions of nixpkgs instead of just source code, that are actually pinned) | 21:18:11 |
| infinisil | At least programs.sqlite clearly demonstrates that channels can have huge value. And flakes could make use of that too | 21:18:33 |
| infinisil | I like how npins supports channels natively | 21:19:44 |
| infinisil | So if you do npins add channel nixpkgs-unstable and use the resulting Nixpkgs to build your NixOS system, you get an prebuilt always-up-to-date binary lookup for free! | 21:20:20 |
| infinisil | Without nix-channel! | 21:20:43 |
|  ma27 joined the room. | 21:47:40 |
 tomberek | Apologies for the re-start of a topic, but regarding the mentions above for makeScope, I've experimented with a variant of it that can be used with nested attrsets that was quite pleasant to use (ie; the // was not destructive and allowed for adding things to pythonPackages in a composable manner). +1 on the topic of improving the usage of package sets. | 22:48:13 |
