Using these few lines of polyfill should help avoid end user's
flake.lock being polluted with sometimes hard to deduplicate
dependencies (i.e., ghostty)
This is the best practice for Flakes or clients of nixpkgs in general.
The `release-<YY.MM>` branch is actually a dev branch:
Hydra continually tests the tip of this branch.
When the tests succeed, the `nixos-<YY.MM>` release branch is updated to
point to the succeeding commit.
`release-<YY.MM>` is to `nixos-<YY.MM>` what `master` is to `nixpkgs-unstable`.
See also: e88fb997e3/CONTRIBUTING.md (flow-of-merged-pull-requests)
This is a small change to a comment in flake.nix. The comment recommend using `zigpkgs.master.latest` which doesn't exist when I tried using the overlay.