context for introducing runtime dependencies

The first occurrence of "runtime dependencies" wasn't related to the surrounding narrative.
This commit is contained in:
Dan Connolly 2016-02-18 23:29:00 -06:00
parent 7251a81bde
commit b39ec410ee

View file

@ -62,9 +62,10 @@ directories such as
so if a package builds correctly on your system, this is because you so if a package builds correctly on your system, this is because you
specified the dependency explicitly.</para> specified the dependency explicitly.</para>
<para>Runtime dependencies are found by scanning binaries for the hash <para>Once a package is built, runtime dependencies are found by
parts of Nix store paths (such as <literal>r8vvq9kq…</literal>). This scanning binaries for the hash parts of Nix store paths (such as
sounds risky, but it works extremely well.</para> <literal>r8vvq9kq…</literal>). This sounds risky, but it works
extremely well.</para>
</simplesect> </simplesect>