Still on 22.11 with various cherry-picked commits from unstable. Will switch to 23.05 when I have some spare time.
this post was submitted on 09 Jun 2023
1 points (100.0% liked)
nixos
1262 readers
8 users here now
All about NixOS - https://nixos.org/
founded 4 years ago
Unstable always. Very rarely the build breaks, but that just means I can't update my systems for a few days. Due to the atomic updates, my systems themselves have never broken.
I use a fork (with some stuff I haven't cleaned up enough to PR) that I rebase on master whenever I decide to upgrade, because I like maximum pain.
Although honestly it's still really stable. When something breaks, it's usually easy to bisect and fix.
You basically use master? Holy sh*t dude, good luck with that.
If you just want to have some packages that aren't in nixpkgs, then why not just create a custom flake?
Well I'm only just trying to move to flakes now. I've had this process in place for years.
I do have some packages in overlay form, but the nixpks changes are things that should be upstreamed at some point. They mostly either have open PRs or aren't cleaned up enough to PR.
https://github.com/corngood/nixpkgs/commits/master
That's the actual branch where I merge in my changes.
Here's a random example of a change:
https://github.com/corngood/nixpkgs/commit/fc12baf28104d63fc163e9afe2aea24409522729
I find it much easier to maintain something like that as a patch, rather than an overlay (if that's even possible).
Is there a reason you rebase on master instead of just unstable?
I find it very easy to bisect and fix problems in nixpkgs, and it seems like a good way to contribute. I can do upgrades whenever I feel like it, and it's trivial to roll back, so it's never blocking me when I need to get other work done.