| 31 Mar 2025 |
 emily | it's the specific way it's done and the communication around it and the timing and the lack of attention to back compat | 21:08:10 |
| emily | i get that this is frustrating on your end too but the first most of us heard of this packaging was when 2.26 got merged with it | 21:08:40 |
 John Ericson | and so now it's painful to see when I felt so close to being done these herdles | 21:08:41 |
| emily | just like the first we heard of the plan to do another Nix bump was when a comment got edited a few hours ago | 21:09:00 |
| John Ericson | hell, even when I am doing other things in Nixpkgs like the compilers and hte libs and whatnot, it is often breaking up packages into smaller packages | 21:09:09 |
| emily | and I let the packaging topic drop since I've had other commitments and shipping a problematic nixVersions.latest isn't the end of the world even if ideally avoidable | 21:09:58 |
| emily | if I'd known it was going to go fix cross -> bump latest -> bump default over a few days leading up to freeze I'd have pressed the points harder | 21:10:32 |
| John Ericson | fix cross is good, right? | 21:11:38 |
| emily | of course. though the first time it broke the channel but that's on our current CI | 21:12:03 |
| John Ericson | I depsartely need to eat in a moment, but also, what exactly do you (and anyone else) imagine the split package is going to break? | 21:12:03 |
| John Ericson | (we've seen the issues with the combo packgae and symlinks) | 21:12:13 |
| emily | my point is that it was totally unshippable days ago | 21:12:18 |
