From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/4] build: Add more variables to (guix config).
Date: Tue, 18 Aug 2015 17:15:04 +0200 [thread overview]
Message-ID: <87egj0r5l3.fsf@gnu.org> (raw)
In-Reply-To: <1438033720-30958-2-git-send-email-mthl@openmailbox.org> (Mathieu Lirzin's message of "Mon, 27 Jul 2015 23:48:37 +0200")
Mathieu Lirzin <mthl@openmailbox.org> skribis:
> * guix/config.scm.in (%prefix, %guile-module-dir): New variables.
In general augmenting (guix config) is problematic because of the way
‘guix pull’ works: (guix config) is always preserved, so if the pulled
code expects new variables there, it may be disappointed.
Ludo’.
next prev parent reply other threads:[~2015-08-18 15:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 21:48 [PATCH 0/4] Emacs Interface build system Mathieu Lirzin
2015-07-27 21:48 ` [PATCH 1/4] build: Add more variables to (guix config) Mathieu Lirzin
2015-07-29 8:35 ` Alex Kost
2015-08-06 17:38 ` Mathieu Lirzin
2015-08-18 15:15 ` Ludovic Courtès [this message]
2015-08-25 21:14 ` Mathieu Lirzin
2015-07-27 21:48 ` [PATCH 2/4] build: Produce 'guix-config' instead of using compile-time tricks Mathieu Lirzin
2015-07-27 21:56 ` Mathieu Lirzin
2015-07-29 8:35 ` Alex Kost
2015-08-06 17:50 ` Mathieu Lirzin
2015-08-13 8:04 ` Alex Kost
2015-08-25 21:16 ` Mathieu Lirzin
2015-08-26 10:51 ` Alex Kost
2015-08-30 17:55 ` Mathieu Lirzin
2015-08-30 19:03 ` Alex Kost
2015-07-27 21:48 ` [PATCH 3/4] emacs: Move guix-guile-program to 'guix-config' Mathieu Lirzin
2015-07-29 8:36 ` Alex Kost
2015-08-06 17:55 ` Mathieu Lirzin
2015-08-07 7:21 ` Alex Kost
2015-08-25 21:18 ` Mathieu Lirzin
2015-08-30 17:32 ` Ludovic Courtès
2015-08-30 19:03 ` Alex Kost
2015-08-30 20:54 ` Mathieu Lirzin
2015-07-27 21:48 ` [PATCH 4/4] emacs: Use only one guix-load-path variable Mathieu Lirzin
2015-07-29 8:36 ` Alex Kost
2015-08-06 17:58 ` Mathieu Lirzin
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87egj0r5l3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mthl@openmailbox.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).