From 3df1ee2ba573a999aebb87cc9c5cac21df158120 Mon Sep 17 00:00:00 2001 From: Valentin Gagarin Date: Thu, 4 Aug 2022 12:32:35 +0200 Subject: [PATCH] clarify what explicitly declaring certain dependencies means --- doc/manual/src/architecture/store/path.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/manual/src/architecture/store/path.md b/doc/manual/src/architecture/store/path.md index 7d793749b..3b14b2f3c 100644 --- a/doc/manual/src/architecture/store/path.md +++ b/doc/manual/src/architecture/store/path.md @@ -81,7 +81,7 @@ This way, scanning files captures run time dependencies without the user having Doing it at build time and persisting references in the store object avoids repeating this time-consuming operation. ::: {.note} -In practice, it is sometimes still necessary to declare certain dependencies explicitly, if they are to be preserved in the build result's closure. +In practice, it is sometimes still necessary for users to declare certain dependencies explicitly, if they are to be preserved in the build result's closure. This depends on the specifics of the software to build and run. For example, Java programs are compressed after compilation, which obfuscates any store paths they may refer to and prevents Nix from automatically detecting them.