| 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 |
| Growpotkin | It's a wicked useful routine and it's subparts are also incredibly useful in isolation.
In nixpkgs the parts are always used as a single long pipe, but dream2nix, floco, and hella other `nix` frameworks have needed to rewrite subparts of `makeScope` because it's one pipe | 22:54:21 |
| 9 Mar 2024 |
| @jade_:matrix.org | i had to stare it down to make a subsidiary scope of a customized pythonPackages. very wacky function, infinite appreciation to Valentin for getting a docs pr happening for it | 00:22:29 |
 raitobezarius | maybe of note: https://github.com/NixOS/nixpkgs/pull/87388 | 00:23:35 |
| raitobezarius | and I realize I missed to answer to Valentin's message here 🤦♂️ | 00:23:43 |
|  Yinfeng joined the room. | 02:27:52 |
|  Benedikt joined the room. | 15:38:13 |
| 10 Mar 2024 |
 fgaz | FYI I'm working on a phorge package and module, hopefully I'll publish it soon | 06:46:24 |
 @adis:blad.is | You can't do that with Python specifically because of collisions | 07:00:34 |
| @adis:blad.is | To actually accomplish that for Python packages you need to get rid of dependency propagation | 07:01:31 |
| @adis:blad.is | See https://github.com/NixOS/nixpkgs/issues/272178 & https://github.com/NixOS/nixpkgs/pull/272179 in particular | 07:02:05 |
|  @eyjhb:eyjhb.dk joined the room. | 10:27:12 |
 Philip Taron (UTC-8) | Add me as a reviewer! 😍 | 13:24:55 |
| 11 Mar 2024 |
|  @cf11:0x2c.org changed their display name from flo to chaoflow. | 07:48:26 |
| infinisil | In reply to @infinisil:matrix.org
Anyways I'll soon share the logs of that room, it's really not very exciting. In summary it's:
- Getting everybody to approve two new members
- Me using the @ room ping in that channel to easily ping all members and ask for a new meeting time after the members were accepted
- Me lamenting about the team not working and drafting the announcement to dissolve it
nbp jonringer: Now uploaded the logs here if you're curious :) | 16:18:01 |
 @jonringer:matrix.org | Transparency is always appreciated. Thank you. | 16:18:53 |
| @jonringer:matrix.org | I understand that doing candidate selection can be sensitive. I would be fine with some discretion. I think I was more advocating for a statement like,
The Nixpkgs Architecture team met, and unanimously decides to move foward with both candidates. We are happy to welcome <personA> and <personB> to our team.
If someone was passed over, just a civil statement as to why I think would suffice.
Sorry if my paranoia in some opaque community interactions spilled over into other teams.
| 16:31:11 |
