From 9d155d9fbee35ac05fca98f390866b31ccd48eae Mon Sep 17 00:00:00 2001 From: Noam Yorav-Raphael Date: Wed, 10 Apr 2024 18:57:15 +0300 Subject: [PATCH] Update 07-working-derivation.md - "input derivations" -> "input sources" The text says that `builder.sh` is in the input derivations. It's actually in `inputSrcs`, not `inputDrvs`. Perhaps in the past there was just one list? --- pills/07-working-derivation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pills/07-working-derivation.md b/pills/07-working-derivation.md index 3a49710..b1d2ffe 100644 --- a/pills/07-working-derivation.md +++ b/pills/07-working-derivation.md @@ -132,7 +132,7 @@ $ nix derivation show /nix/store/i76pr1cz0za3i9r6xq518bqqvd2raspw-foo.drv } ``` -Much like the usual .drv, except that there's a list of arguments in there passed to the builder (bash) with `builder.sh`... In the nix store..? Nix automatically copies files or directories needed for the build into the store to ensure that they are not changed during the build process and that the deployment is stateless and independent of the building machine. `builder.sh` is not only in the arguments passed to the builder, it's also in the input derivations. +Much like the usual .drv, except that there's a list of arguments in there passed to the builder (bash) with `builder.sh`... In the nix store..? Nix automatically copies files or directories needed for the build into the store to ensure that they are not changed during the build process and that the deployment is stateless and independent of the building machine. `builder.sh` is not only in the arguments passed to the builder, it's also in the input sources. Given that `builder.sh` is a plain file, it has no .drv associated with it. The store path is computed based on the filename and on the hash of its contents. Store paths are covered in detail in [a later pill](18-nix-store-paths.md).