| 8 Mar 2024 |
 Jonas Chevalier | One of the hard part of getting large projects done is to find the right people. People you get along with and that are going to augment you. One bad apple can easily disrupt a project. That bad apple might be a good fit for other people so it's not a judgement. But it makes sense to me to select people in private. | 18:10:40 |
|  @patka_123:matrix.org joined the room. | 18:14:08 |
 nbp | For having joined NixOS when there was less people than this channel has, … sometimes you just deal we who is there.
But I do agree that when you have the luxury of making a cohesive team which can work well together this can yield a better outcome, but I am not sure this can easily be judged without already knowing the persons. | 18:15:04 |
| nbp | * For having joined NixOS when there was less people than this channel has, … sometimes you just deal we who is there.
But I do agree that when you have the luxury of making a cohesive team which can work well together this can yield a better outcome, however I am not sure this can easily be judged without already knowing the persons. | 18:15:30 |
|  hexa joined the room. | 18:15:43 |
| nbp | (and I should have stopped commenting as this room is about Nixpkgs Architecture) | 18:16:12 |
| Jonas Chevalier | good call, what is the next architecture change we should make? | 18:16:45 |
| nbp | S.O.S. then grafting 🙄 | 18:17:15 |
 infinisil | I'll personally finish pkgs/by-name first, then improving it to also be usable for multiple package versions and other package sets :) | 18:18:27 |
 Minijackson | about pkgs/by-name, is there a way to use that pattern outside of nixpkgs? Are the utility functions exported somewhere? | 18:20:03 |
| Minijackson | I think it'd be a really nice improvements in my own projects | 18:20:34 |
| infinisil | Minijackson: You can fairly easily use the basic pattern. The tricky bit is ensuring it's correct, though even that can be implemented fairly easily just in Nix. Nixpkgs has unique constraints that make it much trickier to do that | 18:22:11 |
| infinisil | Minijackson: This is the most basic thing you could use/copy: https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/by-name-overlay.nix
The sharding doesn't make a lot of sense when you don't have a lot of packages, so I recommend just removing that for personal use
| 18:23:16 |
| infinisil | Really at that point it's just a mapAttrs (name: _: callPackage (./ + "${name}") { }) (readDir ./.) | 18:23:56 |
| infinisil | Fairly standard pattern already :) | 18:24:08 |
| Minijackson | thanks a lot! | 18:24:27 |
|  @julienmalka:matrix.org joined the room. | 18:39:37 |
|  @janik0:matrix.org joined the room. | 18:55:10 |
|  jakegrin joined the room. | 19:30:57 |
|  rick.special joined the room. | 19:31:35 |
|  @me:indeednotjames.com joined the room. | 19:40:34 |
 @jade_:matrix.org | I just filed: https://github.com/NixOS/nixpkgs/pull/294353
In writing this I realized that we have both makeExtensible and makeScope. Is there any reason to use makeScope over makeExtensible? Have we written down somewhere secret which one to use in which cases? | 20:46:54 |
