Commit graph

7 commits

Author SHA1 Message Date
seth
7dd1f3eda2
drop flake-utils
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)
2024-11-16 05:31:03 -05:00
山下
b03592ac17 Revert back to nixpkgs 23.11 and update flake lockfile 2024-02-19 21:33:12 +09:00
Erik Arvstedt
475dda08b5 flakes: use stable release branches for nixpkgs inputs
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)
2023-12-17 21:33:53 +01:00
Mitchell Hashimoto
7166fe436b
update to nix 23.05 2023-07-11 14:40:15 -07:00
Mitchell Hashimoto
03177b00df
Add a shell.nix 2023-01-17 09:37:23 -08:00
Mitchell Hashimoto
1d737fcd29
update the flake lock 2022-08-22 19:42:12 -07:00
Mitchell Hashimoto
223a4e3b2c
Initial commit based on original arqv repository 2022-08-22 15:56:44 -07:00