| 8 Mar 2024 |
 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 |
 adisbladis | You can't do that with Python specifically because of collisions | 07:00:34 |
| adisbladis | To actually accomplish that for Python packages you need to get rid of dependency propagation | 07:01:31 |
| adisbladis | 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 |
| infinisil | Yeah, I was only able to disclose it in full this time because nothing personal was being discussed, definitely shouldn't become standard | 16:38:39 |
 nbp | I second the feeling. Thanks for doing this extra effort and keeping the other channel on track. | 17:01:14 |
| nbp | * I second the feeling. Thanks for doing this extra effort and keeping the other channel on topic. | 17:01:19 |
| infinisil changed the room topic to "Discussions about Nixpkgs' architecture - https://github.com/NixOS/nixpkgs/labels/architecture" from "https://nixos.org/community/teams/nixpkgs-architecture.html -https://www.youtube.com/@nixpkgs-architecture". | 17:06:51 |
| 12 Mar 2024 |
|  @benjaminedwardwebb:envs.net joined the room. | 02:38:19 |
| 13 Mar 2024 |
|  @ktemkin:katesiria.org changed their display name from Kate Temkin to [K]ate Temkin. | 02:56:13 |
| 14 Mar 2024 |
|  @federicodschonborn:matrix.org left the room. | 02:04:38 |
|  NixOS Moderation Botchanged room power levels. | 18:44:58 |
| infinisil | Philip Taron (UTC-8): Just a minor comment: https://github.com/NixOS/nixpkgs/pull/293901#discussion_r1525395621 | 19:34:13 |
| Philip Taron (UTC-8) | Thanks! 👀 | 19:34:45 |
| Philip Taron (UTC-8) |
What's the reason behind using lib only for some fields but lib.<sublib> for others? E.g. attrNames comes from lib, but isDerivation comes from lib.attrsets, even though they're available in both.
Dang, I still struggle with this in lib. If there is a rhyme or reason for having some names be re-exported from lib vs. some names being only available in lib.sublib, I can't find it.
| 19:36:19 |
