From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@gmail.com>
Cc: guix <guix-devel@gnu.org>, Feng Shu <tumashu@163.com>
Subject: Re: How can I add a package outside the guix source dir?
Date: Fri, 22 May 2015 16:22:50 +0200 [thread overview]
Message-ID: <87siaoitdx.fsf@gnu.org> (raw)
In-Reply-To: <871ti8q0z9.fsf@gmail.com> ("宋文武"'s message of "Fri, 22 May 2015 19:56:58 +0800")
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
宋文武 <iyzsong@gmail.com> skribis:
> Feng Shu <tumashu@163.com> writes:
>
>> taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:
[...]
>>> See (info "(guix) Package Modules"),
>>> i.e. https://gnu.org/s/guix/manual/html_node/Package-Modules.html
> The manual does mention it as (17), but it's not very clear how to do
> it right.
I have pushed a clarification.
Thanks for your feedback,
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1310 bytes --]
--- 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)}@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
+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
+@code{GUIX_PACKAGE_PATH}. @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
+@code{-e} 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
next prev parent reply other threads:[~2015-05-22 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 8:37 How can I add a package outside the guix source dir? Feng Shu
2015-05-22 9:01 ` Taylan Ulrich Bayırlı/Kammer
2015-05-22 11:05 ` Feng Shu
2015-05-22 11:56 ` 宋文武
2015-05-22 14:22 ` Ludovic Courtès [this message]
2015-05-22 9:01 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87siaoitdx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@gmail.com \
--cc=tumashu@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.