01/01: doc: Clarify the module file name convention.

[Ludovic Courtès]

civodul pushed a commit to branch master
in repository guix.

commit c95ded7ed6938aa5aaa9abce81d87b2d6dbc7aa7
Author: Ludovic Courtès <address@hidden>
Date:   Fri May 22 16:20:04 2015 +0200

    doc: Clarify the module file name convention.
    
    * doc/guix.texi (Package Modules): Clarify the footnote about the module 
file
      names convention.  Tweak the wording.
---
 doc/guix.texi |   10 +++++++---
 1 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 53761df..9bd9c58 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -6154,11 +6154,15 @@ facility is implemented in the @code{(gnu packages)} 
module.
 @cindex package module search path
 Users can store package definitions in modules with different
 names---e.g., @code{(my-packages emacs)address@hidden 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
+name and module name must match.  For instance, the @code{(my-packages
+emacs)} module must be stored in a @file{my-packages/emacs.scm} file
+relative to the load path specified with @option{--load-path} or
address@hidden  @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
address@hidden option so that they know where to find the package, or use the
address@hidden option so that they know where to find the package.  Better
+yet, they can use the
 @code{-L} option of these commands to make those modules visible
 (@pxref{Invoking guix build, @code{--load-path}}), or define the
 @code{GUIX_PACKAGE_PATH} environment variable.  This environment