aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2015-04-07 22:53:06 +0200
committerLudovic Courtès <ludo@gnu.org>2015-04-07 22:53:06 +0200
commit60142854af39e03a00bb2ab12f4710ec4311a4b7 (patch)
tree2475b76ec09acb1b207d85f0f868f337b6f60229
parent391bdd8f7f6db2873647e566f5a5570b4eb59c62 (diff)
downloadgnu-guix-60142854af39e03a00bb2ab12f4710ec4311a4b7.tar
gnu-guix-60142854af39e03a00bb2ab12f4710ec4311a4b7.tar.gz
doc: Mention the relation between module names and file names.
* doc/guix.texi (Package Modules): Mention the relation between module names and file names.
-rw-r--r--doc/guix.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index 85e8243015..2997978582 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5439,7 +5439,9 @@ facility is implemented in the @code{(gnu packages)} module.
@cindex customization, of packages
@cindex package module search path
Users can store package definitions in modules with different
-names---e.g., @code{(my-packages emacs)}. These package definitions
+names---e.g., @code{(my-packages emacs)}@footnote{Note that the file
+name and module name must match. @xref{Modules and the File System,,,
+guile, GNU Guile Reference Manual}, for details.} These package definitions
will not be visible by default. Thus, users can invoke commands such as
@command{guix package} and @command{guix build} have to be used with the
@code{-e} option so that they know where to find the package, or use the