From b159d08ae3efc2fc6c01c9d3be6bf4423d3970e0 Mon Sep 17 00:00:00 2001 From: Attila Gulyas Date: Wed, 14 Aug 2024 18:05:53 -0400 Subject: [PATCH] Update towards-reproducibility-pinning-nixpkgs.md (#1029) I expected the `` link to point to a resource that explains what that construct is and not directly to Nixpkgs. If I would be totally new to Nix, that would be even more confusing. --- .../first-steps/towards-reproducibility-pinning-nixpkgs.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/source/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs.md b/source/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs.md index 481ffd476..08707e336 100644 --- a/source/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs.md +++ b/source/tutorials/first-steps/towards-reproducibility-pinning-nixpkgs.md @@ -2,7 +2,7 @@ # Towards reproducibility: pinning Nixpkgs -In various Nix examples, you'll often see references to [\](https://github.com/NixOS/nixpkgs), as follows. +In various Nix examples, you'll often see the following: ```nix { pkgs ? import {} }: @@ -10,6 +10,11 @@ In various Nix examples, you'll often see references to [\](https://git ... ``` +:::{note} +`` points to the file system path of some revision of {term}`Nixpkgs`. +Find more information on [lookup paths](lookup-path-tutorial) in [](reading-nix-language). +::: + This is a **convenient** way to quickly demonstrate a Nix expression and get it working by importing Nix packages. However, **the resulting Nix expression is not fully reproducible**.