You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/nix-installation.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ To use flakes there are two things we need to do:
93
93
1. make sure the version of Nix we're on is at least 2.4
94
94
2. enable both the `nix-command` and `flakes` experimental features.
95
95
96
-
Since the latest release of Nix is already at 2.21, if you installed Nix recently as per the instructions above, you should be on a recent-enough version:
96
+
Since the latest release of Nix is already at 2.22, if you installed Nix recently as per the instructions above, you should be on a recent-enough version:
Copy file name to clipboardExpand all lines: doc/nix-usage-flakes.md
+8-8
Original file line number
Diff line number
Diff line change
@@ -91,7 +91,7 @@ nix registry list
91
91
92
92
For example, rather than referencing the flake on the `nixpkgs-unstable` branch of the Nixpkgs GitHub repository with `github:NixOS/nixpkgs/nixpkgs-unstable`, we can use the simpler identifier `nixpkgs`.
93
93
94
-
If we want to point to a different branch but still use an identifier from the registry, we can do so by extending it with the branch. For example, the flakes identifier `nixpkgs` is the same as `nixpkgs/nixpkgs-ustable`, but we can also use `nixpkgs/nixos-23.11` to override the branch and point to the NixOS 23.11 release branch.
94
+
If we want to point to a different branch but still use an identifier from the registry, we can do so by extending it with the branch. For example, the flakes identifier `nixpkgs` is the same as `nixpkgs/nixpkgs-ustable`, but we can also use `nixpkgs/nixos-24.05` to override the branch and point to the NixOS 24.05 release branch.
95
95
96
96
Note that registries have mutable references, but Nix knows how to rebuild the snapshot referenced for some of these references deterministically. For example, when referencing a GitHub repository via a registry reference, Nix will take note of the commit ID of the snapshot retrieved. Nix typically stores this information required for reproducibility in a *lock file* called `flake.lock` adjacent to `flake.nix`.
GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
227
227
228
-
Here `/nixos-23.11` overrides the default `nixpkgs-unstable` branch of the registry entry, and the `#wezterm` suffix searches not just the flake, but a specific package named `wezterm`, which will either be found or not (there's no need for regexes to filter further).
228
+
Here `/nixos-24.05` overrides the default `nixpkgs-unstable` branch of the registry entry, and the `#wezterm` suffix searches not just the flake, but a specific package named `wezterm`, which will either be found or not (there's no need for regexes to filter further).
229
229
230
230
You may also notice that the Nixpkgs flake outputs packages under the `legacyPackages` attribute instead of the `packages`. The primary difference is that packages are flatly organized under `packages`, while `legacyPackages` can be an arbitrary tree. `legacyPackages` exists specifically for the Nixpkgs project, a central project to the Nix ecosystem that has existed long before flakes. Beyond Nixpkgs, you don't have to think much about `legacyPackages`. Packages from all other flakes should generally be found under `packages`.
231
231
@@ -262,7 +262,7 @@ After a successful call of `nix build`, you'll see one or more symlinks for each
0 commit comments