| 31 Mar 2025 |
 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 |
| John Ericson | (those are now fixed but there could be more) | 21:12:22 |
| John Ericson | I am not contesting that | 21:12:44 |
| John Ericson | I am basically asking "if we make it shippable, are there more unknown-unknowns, or is it good now?" | 21:13:06 |
| John Ericson | IMO risk from unknown-unknowns and risk from known-knowns like "wtf is this unreadable code" are quite different | 21:13:50 |
| John Ericson | the latter can just be fixed, and then it's good, the former is what needs time to incubate | 21:14:02 |
| emily | In reply to @Ericson2314:matrix.org
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? overrides are the big one, esp for patches. and yes, the output shimming seems brittle to me, e.g. I am not sure it works with ^ or the like? the other thing is that the support code is complicated beyond any other non-compiler package set I've seen, but maybe devendoring will help that | 21:14:13 |
| emily | is it really so unreasonable to want to see one uneventful early-cycle Nix bump before we start doing them in the lead up to release coupled with breaking package rewrites? | 21:15:20 |
| emily | even 2.24 took a couple tries to stick | 21:15:30 |
| emily | and I advocated for that bump | 21:15:37 |
| emily | because I don't think the drift is good for the projects | 21:15:49 |
| emily | but the only way to solve the root cause is proactive communication and prioritization of Nixpkgs' needs and concerns for a critical component | 21:16:19 |
| John Ericson | Ultimately I will prioritize a good healthy working relationship over not delaying the split package 6 months more | 21:17:05 |
| John Ericson | but please ask yourself | 21:17:08 |
| John Ericson | the list of things above | 21:17:12 |
| John Ericson | it looks entirely like static known issues to me | 21:17:23 |
| John Ericson | I am a bit scared for 2.28 right now, yes, because that is where unknown-unknowns come from | 21:17:39 |
| John Ericson | but you already proposed we do just that (and monopackage) | 21:17:53 |
| emily | nothing blocks shipping a patching mechanism that works with both packagings in 25.06 and backporting to 24.11, right? | 21:18:00 |
| John Ericson | the marginial cost of the split package feels very low to me | 21:18:09 |
| emily | in which case we would be free to break the old way in 25.11 | 21:18:14 |
| John Ericson | because we can simply test all the things you mentioned right away | 21:18:20 |
| John Ericson | there aren't really latant issues | 21:18:24 |
| John Ericson | you mean a patching mechanism that works with split and unsplit packages? | 21:19:26 |
| John Ericson | I am not sure, probably not | 21:19:31 |
| emily | how people consume our packages is a tragic unknown. though of course we always have to draw a line somewhere but look at how breaking changes to lib are handled for how our caution should increase as the criticality does | 21:19:36 |
| emily | and again if we were keeping packaging constant but bumping version or vice versa (not possible in this case, I know), there would still be concerns but of lower magnitude | 21:20:18 |
