d889861c21
- NixOS automatically manages the flake registry because I fixed it. - Clarify that nix-channel does have a spiritual successor in flakes in the form of the registry, but that it's kind of useless.
2.6 KiB
Custom NIX_PATH and Flake Registry
Introduction to NIX_PATH
The Nix search path is controlled by the environment variable NIX_PATH, which follows
the same format as the Linux PATH environment variable, consisting of multiple paths
separated by colons.
Paths in Nix expressions that look like <name> are resolved using the path named name
from the NIX_PATH.
This usage pattern is no longer recommended under the Flakes feature because it results in
Flake builds depending on a mutable environment variable NIX_PATH, compromising
reproducibility.
However, in certain scenarios, we still need to use NIX_PATH, such as when we frequently
use the command nix repl '<nixpkgs>', which utilizes the Nixpkgs found through
NIX_PATH search.
Introduction to Flakes Registry
The Flakes Registry is a center for Flake registration that assists us in using shorter
IDs instead of lengthy flake repository addresses when using commands like nix run,
nix shell, and more.
By default, Nix looks up the corresponding GitHub repository address for this ID from https://github.com/NixOS/flake-registry/blob/master/flake-registry.json.
For instance, if we execute nix run nixpkgs#ponysay hello, Nix will automatically
retrieve the GitHub repository address for nixpkgs from the aforementioned JSON file. It
then downloads the repository, locates the flake.nix within, and runs the corresponding
ponysay package.
Custom NIX_PATH and Flake Registry
NOTE: Newcomers should skip this section! Disabling
nix-channelincorrectly may lead to some headaches.
The roles of NIX_PATH and the Flake Registry have been explained earlier. In daily use,
we typically want the nixpkgs used in commands like nix repl '<nixpkgs>',
nix run nixpkgs#ponysay hello to match the system's nixpkgs. This is done
by default as of NixOS 24.05. Also, although
nix-channel can coexist with the Flakes feature, in practice, Flakes can
completely replace it, so we can also disable it.
In your NixOS configuration, adding the following module will achieve the mentioned requirements:
{ nixpkgs, ... }: {
nix.channel.enable = false; # remove nix-channel related tools & configs, we use flakes instead.
# this is set automatically by nixpkgs.lib.nixosSystem but might be required
# if one is not using that:
# nixpkgs.flake.source = nixpkgs;
}