mirror of
https://github.com/privatevoid-net/nix-super.git
synced 2024-11-25 15:26:17 +02:00
clarify what explicitly declaring certain dependencies means
This commit is contained in:
parent
b7309ce624
commit
3df1ee2ba5
1 changed files with 1 additions and 1 deletions
|
@ -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.
|
||||||
|
|
Loading…
Reference in a new issue