diff options
author | Ludovic Courtès <ludo@gnu.org> | 2014-01-17 22:52:10 +0100 |
---|---|---|
committer | Ludovic Courtès <ludo@gnu.org> | 2014-01-17 22:52:10 +0100 |
commit | 7e17f65d9581277298282fc6014a8de37293788b (patch) | |
tree | 99f584c23c49e9e25051652fa45a4697555889a9 /doc | |
parent | c5e0eb28845dc1f01ab5b4e81ee6596a23223ede (diff) | |
download | patches-7e17f65d9581277298282fc6014a8de37293788b.tar patches-7e17f65d9581277298282fc6014a8de37293788b.tar.gz |
doc: Distinguish between (gnu packages ...) and "GNU packages".
* doc/guix.texi (Package Modules): Add a footnote stating that (gnu
packages ...) has nothing to do with "GNU packages."
Diffstat (limited to 'doc')
-rw-r--r-- | doc/guix.texi | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/guix.texi b/doc/guix.texi index 0a06ddc4c4..2081dd13ad 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -1978,7 +1978,12 @@ the load. To check whether a package has a @code{debug} output, use From a programming viewpoint, the package definitions of the distribution are provided by Guile modules in the @code{(gnu packages -...)} name space (@pxref{Modules, Guile modules,, guile, GNU Guile +@dots{})} name space@footnote{Note that packages under the @code{(gnu +packages @dots{})} module name space are not necessarily ``GNU +packages''. This module naming scheme follows the usual Guile module +naming convention: @code{gnu} means that these modules are distributed +as part of the GNU system, and @code{packages} identifies modules that +define packages.} (@pxref{Modules, Guile modules,, guile, GNU Guile Reference Manual}). For instance, the @code{(gnu packages emacs)} module exports a variable named @code{emacs}, which is bound to a @code{<package>} object (@pxref{Defining Packages}). The @code{(gnu |