nrabulinski/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity

clarify what explicitly declaring certain dependencies means

Browse source
This commit is contained in:
Valentin Gagarin 2022-08-04 12:32:35 +02:00 committed by Valentin Gagarin
parent b7309ce624
commit 3df1ee2ba5
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/manual/src/architecture/store/path.md
View file

@ -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. Doing it at build time and persisting references in the store object avoids repeating this time-consuming operation.
::: {.note} ::: {.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. 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. For example, Java programs are compressed after compilation, which obfuscates any store paths they may refer to and prevents Nix from automatically detecting them.