From b39ec410eeb59ed8ae8c2808a79a21578ef801e6 Mon Sep 17 00:00:00 2001 From: Dan Connolly Date: Thu, 18 Feb 2016 23:29:00 -0600 Subject: context for introducing runtime dependencies The first occurrence of "runtime dependencies" wasn't related to the surrounding narrative. --- doc/manual/introduction/about-nix.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/manual/introduction/about-nix.xml b/doc/manual/introduction/about-nix.xml index 66679ac9a85a..0c58984ac489 100644 --- a/doc/manual/introduction/about-nix.xml +++ b/doc/manual/introduction/about-nix.xml @@ -62,9 +62,10 @@ directories such as so if a package builds correctly on your system, this is because you specified the dependency explicitly. -Runtime dependencies are found by scanning binaries for the hash -parts of Nix store paths (such as r8vvq9kq…). This -sounds risky, but it works extremely well. +Once a package is built, runtime dependencies are found by +scanning binaries for the hash parts of Nix store paths (such as +r8vvq9kq…). This sounds risky, but it works +extremely well. -- cgit 1.4.1