From b0fb4ac4c66ea88ab15161665c117237c11ccb2b Mon Sep 17 00:00:00 2001 From: Attila Gulyas Date: Tue, 13 Aug 2024 04:07:59 -0400 Subject: [PATCH] Fix explanation of code snippet (#1028) I presume that at one point there was only one package that was referred from `pkgs` and then another one was added later. --- source/tutorials/first-steps/declarative-shell.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/tutorials/first-steps/declarative-shell.md b/source/tutorials/first-steps/declarative-shell.md index 4a7a777..f097c14 100644 --- a/source/tutorials/first-steps/declarative-shell.md +++ b/source/tutorials/first-steps/declarative-shell.md @@ -74,7 +74,7 @@ Only later it became widely used as a general way to make temporary environments `mkShellNoCC` is a function that produces such an environment, but without a compiler toolchain. `mkShellNoCC` takes as argument an attribute set. -Here we give it an attribute `packages` with a list containing one item from the `pkgs` attribute set. +Here we give it an attribute `packages` with a list containing two items from the `pkgs` attribute set. :::{Dropdown} Side note on `packages` and `buildInputs` You may encounter examples of `mkShell` or `mkShellNoCC` that add packages to the `buildInputs` or `nativeBuildInputs` attributes instead.