From 091c7953851f92fede635884b5a8c80d048a0c04 Mon Sep 17 00:00:00 2001 From: Attila Gulyas Date: Fri, 9 Aug 2024 22:19:57 -0400 Subject: [PATCH] Update declarative-shell.md I presume that at one point there was only one package that was referred from `pkgs` and then another one was added later. Or I misunderstood something and the sentence **is** correct, so perhaps there should be a note there what the one is referring to... Thanks again! --- 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 4a7a7774e..f097c14fb 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.