aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/src/architecture
diff options
context:
space:
mode:
authorValentin Gagarin <valentin@fricklerhandwerk.de>2022-08-04 12:32:35 +0200
committerValentin Gagarin <valentin.gagarin@tweag.io>2022-08-04 12:37:48 +0200
commit3df1ee2ba573a999aebb87cc9c5cac21df158120 (patch)
treefc416ffa2db56dc610f6cd9cad02824654db8369 /doc/manual/src/architecture
parentb7309ce624d17a2dbe97f63700d59830c35b074a (diff)
clarify what explicitly declaring certain dependencies means
Diffstat (limited to 'doc/manual/src/architecture')
-rw-r--r--doc/manual/src/architecture/store/path.md2
1 files changed, 1 insertions, 1 deletions
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.