diff options
| author | Sean Seefried <sean.seefried@gmail.com> | 2018-04-12T09·23+1000 |
|---|---|---|
| committer | Sean Seefried <sean.seefried@gmail.com> | 2018-04-12T09·23+1000 |
| commit | 2ef8f0608caa27d1a92d827f54b54155c89092a8 (patch) | |
| tree | 7eb49aa898dbec9f21d052da4da08003cd06c1e1 /doc/manual/introduction | |
| parent | dc0a542c9f8c839b8437b54fcf1c4b47b0cfba10 (diff) | |
Add to glossary and clarify garbage collection
While trying to understand garbage collection it was not immediately clear that only the runtime dependency closure of output paths would be kept (instead of the build-time dependency closure). This commit attempts to clarify this by expanding some of the glossary definitions and extending the Garbage Collection section.
Diffstat (limited to 'doc/manual/introduction')
| -rw-r--r-- | doc/manual/introduction/about-nix.xml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/manual/introduction/about-nix.xml b/doc/manual/introduction/about-nix.xml index 83a2b6786ac0..e8c0a29753a1 100644 --- a/doc/manual/introduction/about-nix.xml +++ b/doc/manual/introduction/about-nix.xml @@ -60,7 +60,8 @@ This is because tools such as compilers don’t search in per-packages directories such as <filename>/nix/store/5lbfaxb722zp…-openssl-0.9.8d/include</filename>, so if a package builds correctly on your system, this is because you -specified the dependency explicitly.</para> +specified the dependency explicitly. This takes care of the build-time +dependencies.</para> <para>Once a package is built, runtime dependencies are found by scanning binaries for the hash parts of Nix store paths (such as |