>From 9f44c7a847fb9122efc546ae4ad73e53f4fb9214 Mon Sep 17 00:00:00 2001 From: Andreas Enge Date: Wed, 25 Feb 2015 23:55:07 +0100 Subject: [PATCH] doc: Clarify wording for naming of python module packages. * doc/guix.texi (Python Modules): Make clear that the name of a python module package is to be derived from the module name. --- doc/guix.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guix.texi b/doc/guix.texi index 81b9353..2f6f35e 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -2477,7 +2477,7 @@ To illustrate the idea, here is an example of a gexp: #~(begin (mkdir #$output) (chdir #$output) - (symlink (string-append #$coreutils "/bin/ls") + (symlink (string-append #$coreutils "/bin/ls") "list-files"))) @end example @@ -5521,12 +5521,12 @@ seems desirable that the name of a package for a Python module contains the word @code{python}. Some modules are compatible with only one version of Python, others with both. -If the package Foo compiles only with Python 3, we name it +If the module Foo compiles only with Python 3, we name it @code{python-foo}; if it compiles only with Python 2, we name it @code{python2-foo}. If it is compatible with both versions, we create two packages with the corresponding names. -If a project already contains the word @code{python}, we drop this; +If a module name already contains the word @code{python}, we drop this; for instance, the module python-dateutil is packaged under the names @code{python-dateutil} and @code{python2-dateutil}. -- 2.2.1