summary refs log tree commit diff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2014-06-09 18:51:44 +0200
committerLudovic Courtès <ludo@gnu.org>2014-06-09 18:55:48 +0200
commit49ad317ae16abd318d4bb02e0e17260235750b6a (patch)
tree0e48e7c306a5b3de24eef896878a42b496bb9d02
parentf9057dba6aab4712b2c7ba2425c855b9bc4bcabc (diff)
downloadguix-49ad317ae16abd318d4bb02e0e17260235750b6a.tar.gz
doc: Add a few words on the term "derivation".
* doc/guix.texi (Programming Interface): Add a sentence on "derivation".
-rw-r--r--doc/guix.texi3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index 10eb344c71..c1e51eac94 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -1305,7 +1305,8 @@ store.  To instruct the daemon to perform a build action, users actually
 provide it with a @dfn{derivation}.  A derivation is a low-level
 representation of the build actions to be taken, and the environment in
 which they should occur---derivations are to package definitions what
-assembly is to C programs.
+assembly is to C programs.  The term ``derivation'' comes from the fact
+that build results @emph{derive} from them.
 
 This chapter describes all these APIs in turn, starting from high-level
 package definitions.