| 27 Mar 2023 |
 toonn | I just want to make sure I'm following the discussion. | 16:57:01 |
 infinisil | toonn: Oh yeah it's the current module system used for NixOS | 16:59:34 |
 nbp | In reply to @infinisil:matrix.org
nbp: Wait in your proposal, can SOS be used outside of Nixpkgs by third-parties? Iirc it can't Nixpkgs based on S.O.S. can be used by third-parties.
However, it only solve the overriding issues within the Nixpkgs fix-point, i.e. if you want to override Nixpkgs packages, you would either use an overlay to benefit from S.O.S., or use the old way. | 16:59:34 |
| nbp | In reply to @infinisil:matrix.org
If we want to consider doing SOS instead of a module system to solve these problem, then SOS needs to be at least better than the module system at solving these problems. A module system solves a different problem which is either the package configuration and/or the package setup. These problems are orthogonal to S.O.S., and should probably be evaluated separately. | 17:01:48 |
| infinisil | nbp: I see, I'll definitely take another look at SOS and I might bring it up in the working group. I added it in https://discourse.nixos.org/t/working-group-member-search-module-system-for-packages/26574#previous-work-3 | 17:03:59 |
| nbp | Thus this would not be instead, but in addition to. Unless you want a single module system for Nixpkgs, instead of having one for each package. The problem of having a single module system for the entire Nixpkgs is that you are seting up the ground for something Nixpkgs kind of deliberately avoided, which is the combinatorial complexity of configurations.
In any cases, such module system would be easier to add after S.O.S. | 17:04:20 |
| nbp | * Thus this would not be instead, but in addition to. Unless you want a single module system for Nixpkgs, instead of having one for each package. The problem of having a single module system for the entire Nixpkgs is that you are seting up the ground for something Nixpkgs kind of deliberately avoided, which is the complexity of configurations.
In any cases, such module system would be easier to add after S.O.S. | 17:06:04 |
| infinisil | nbp: I kind of see what you mean yeah, the module system (in its current form) doesn't seem to solve the problem very well | 17:11:40 |
| infinisil | * nbp: I kind of see what you mean yeah, the module system (in its current form) doesn't seem to solve the problem of configs very well | 17:11:51 |
| nbp | The Module System does not solve any constraints, nor configure anything. It only combine configurations.
What most people expect from package managers is to choose between conflicting versions, which Nixpkgs avoided so far, or these have been hard-coded using some of the override functions and multiple installs from Nix. | 17:17:08 |
| nbp | Solving constraints between packages configuration is the source of the complexity I had mentioned previously, behind having a single module system for all of Nixpkgs. | 17:18:31 |
| nbp | If you do not plan on solving constraints, then you are going to have assertions or conflicting configuration which are left to the user to resolve. | 17:19:23 |
| 29 Mar 2023 |
|  prescientmoon joined the room. | 13:25:50 |
 snowytrees | Reading nbp 's comment (https://github.com/NixOS/rfcs/pull/3#issuecomment-370151582) in the RFC after eelco introduced his configurations idea (https://gist.github.com/edolstra/29ce9d8ea399b703a7023073b0dbc00d) cleared up a lot for me how you can build on SOS. Dropping the link because it was pretty deep in the comments | 15:22:36 |
| 2 Apr 2023 |
 tea | Has something like doing nixpkgs-review on github actions been tried out yet? | 14:41:59 |
| tea | would speed up time to merge and complexity by a lot | 14:42:10 |
 Alyssa Ross | there's nowhere near enough capacity, is there? | 14:42:28 |
| Alyssa Ross | i feel like somebody was talking about this in another room the other day | 14:42:45 |
| tea | In reply to @qyliss:fairydust.space
there's nowhere near enough capacity, is there? capacity =? | 14:43:08 |
| Alyssa Ross | wait it was you who was having this conversation | 14:43:25 |
| tea | where? | 14:44:08 |
| Alyssa Ross | in #tvl | 14:44:19 |
| Alyssa Ross | 2023-03-26 | 14:44:24 |
| tea | this is for nixpkgs-review and not nixpkgs as a whole | 14:44:28 |
| Alyssa Ross | assuming you're tea|m | 14:44:28 |
| tea | yes | 14:44:32 |
| tea | there is a limit of 20 concurrent jobs which would get really jammed | 14:44:48 |
| tea | so maybe we'd need to filter somehow | 14:44:55 |
| Alyssa Ross | yeah | 14:45:06 |
| Alyssa Ross | nixpkgs-review is often huge | 14:45:11 |
