| 12 Sep 2023 |
 infinisil | Was a bit hard to keep track of all the PRs/issues | 10:42:21 |
 profpatsch | staging-next should probably just receive a separate formatting commit | 10:50:38 |
| profpatsch | At least in my mind formatting is deterministic, so no further merge conflicts | 10:51:03 |
| infinisil | (this isn't about formatting though) | 10:51:40 |
| infinisil | * (this isn't about formatting fyi) | 10:51:47 |
| profpatsch | oh, then disregard :) | 10:52:40 |
| profpatsch | I read “the automatic migration” and made an ass out of u & me | 10:53:05 |
| infinisil | Haha nah all good | 10:53:27 |
 teto | I watched the pkgs/by-name nix-con talk . At some point it was mentioned that package sets like haskellPackages / luaPackages were out of scope and I was curious if there was work started regarding those package sets (yet). I have some related questions such as "shall we keep everything in one generated.nix file or explode those in xx/PACKAGE/default.nix" | 11:15:07 |
| teto | one of my main problem is that one package that can't be updated (because wrong src etc) will block the generation of the whole package set. I have started working on a workaround with pytreesitter to replace AST nodes when successful but having per-package files has advantages (but I wonder if the sheer number of new files doesn't make it a no-go anyway) | 11:17:11 |
| infinisil | teto: No concrete plans yet. Quick thoughts regarding single vs multiple files: I think multiple files should be preferred regarding git, it should lead to a smaller repo size and make conflicts less frequent | 11:31:00 |
| infinisil |
Check pkgs/by-name / check (pull_request_target) Successful in 46s
Why does this check seem to take longer now 🙃
| 14:54:20 |
