| 8 Mar 2024 |
 @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 |
 Growpotkin | Please - let me split `makeScope` into reusable and well documented helpers.
| 22:50:15 |
| tomberek | and use them in Nixpkgs, to help make everything behave consistently? (asking for a friend ;) ) | 22:51:29 |
| Growpotkin | That function is THE CORE of `nixpkgs` and currently it's really really hard to grok.
It legitimately took me like 6 months of fiddling with similar routines to realize "I just spent months rewriting `makeScope`, and now I actually understand what it was doing" 🤣 | 22:52:04 |
