blog: nixos upstreaming: tweak the wording on `nixos-unstable`

This commit is contained in:
colin 2022-10-14 05:53:23 -07:00
parent 1fca3c633d
commit e4aebca801
1 changed files with 1 additions and 1 deletions

View File

@ -174,6 +174,6 @@ if you're making changes in a hot area of the codebase, the diff from your PR (w
i described here the workflow i found easiest to get started with. with something as configurable as nix, many people use many different workflows. some prefer maintaining their own long-running fork of nixpkgs wherein they cherry-pick all these PRs and periodically rebase against nixos-unstable (or a release branch), and point their flake directly at their fork of nixpkgs. your workflow will surely evolve as you settle in, but hopefully this gives you enough inspiration to get started :-)
finally, don't be afraid to use the `nixos-unstable` branch if you're an intermediate user! it might not be quite as unstable as the name suggests: i've yet to encounter any show-stopping issues, 90% of the instability is just that packages don't build and need to be pinned or fixed (or you skip the update that day). there's a (relatively early) point where the minor inconvenience of nixos-unstable is less than the inconvenience of maintaining patches that have already landed upstream.
finally, don't be overly intimidated by `nixos-unstable` branch. it might not be quite as unstable as the name suggests: i've yet to encounter any show-stopping issues, 90% of the instability is just that packages don't build and need to be pinned or fixed (or you skip the update that day). there's a point where the inconvenience of nixos-unstable is less than the inconvenience of maintaining patches that have already landed upstream. if you're upstreaming enough that you feel that pain point, you'll do fine on the unstable branch.
as always, don't hesitate to [contact me](@/about.md) or reach out on the [forums/chat](https://nixos.org/community/).