| 31 Mar 2025 |
 John Ericson | (e.g. if you need a library, just depend on that library) | 20:37:18 |
| John Ericson | so the exposure of the "everything" package should go down down down | 20:37:31 |
| John Ericson | (for 25.11, I would love to move it to aliases, even) | 20:37:42 |
 emily | In reply to @elvishjerricco:matrix.org
I don't have any issue with the nix version being bumped for 25.05, though leona expressed some concern about it. My issue is with the packaging expressions making it to the default nix in 25.05 even aside from packaging concerns we really do try to avoid major bumps of critical components close to release | 20:38:16 |
| emily | and Nix updates have often been comparably or more painful compared to e.g. major compiler bumps | 20:38:46 |
| emily | i will comment again later once I am no longer on phone keyboard | 20:39:03 |
 ElvishJerricco | I think the fact that Nix is a core component of the OS is a good reason that it should be bumped. We want the default version to be one that's more actively maintained, which a newer version like 2.27 or 2.28 would be. | 20:40:42 |
| emily | it's not going to be the latest for long. the Nix team policy is supporting the latest version and the one in stable Nixpkgs | 20:43:19 |
| John Ericson | emily: I think we've done fairly little feature-behavior churn since 2.24 | 20:43:23 |
| emily | which is their decision of course but it shouldn't impact Nixpkgs release cycle decisions | 20:43:37 |
