From: "Ludovic Courtès" <ludo@gnu.org>
To: Peng Mei Yu <pengmeiyu@riseup.net>
Cc: 41704@debbugs.gnu.org
Subject: [bug#41704] [PATCH V2] services: nix: Set NIX_CONF_DIR environment variable.
Date: Tue, 09 Jun 2020 09:52:04 +0200 [thread overview]
Message-ID: <878sgwoevv.fsf@gnu.org> (raw)
In-Reply-To: <20200604090922.19352-1-pengmeiyu@riseup.net> (Peng Mei Yu's message of "Thu, 4 Jun 2020 17:09:22 +0800")
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
Hi,
Peng Mei Yu <pengmeiyu@riseup.net> skribis:
> * gnu/services/nix.scm (nix-shepherd-service): Set NIX_CONF_DIR environment
> variable to "/etc/nix".
Does the (untested) patch below solve the problem for you?
Perhaps it’s more appropriate than setting NIX_CONF_DIR.
Thanks,
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 602 bytes --]
diff --git a/gnu/packages/package-management.scm b/gnu/packages/package-management.scm
index b1c96f18e7..b3c21473ed 100644
--- a/gnu/packages/package-management.scm
+++ b/gnu/packages/package-management.scm
@@ -551,6 +551,7 @@ out) and returning a package that uses that as its 'source'."
(base32
"1hbqsrp1ii2sfq8x2mahjrl2182qck76n8blrl1jfz3xq99m6i15"))))
(build-system gnu-build-system)
+ (arguments '(#:configure-flags '("--sysconfdir=/etc")))
(native-inputs `(("pkg-config" ,pkg-config)))
(inputs `(("boost" ,boost)
("brotli" ,brotli)
next prev parent reply other threads:[~2020-06-09 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 7:01 [bug#41704] [PATCH] services: nix: Set NIX_CONF_DIR environment variable Peng Mei Yu
2020-06-04 9:09 ` [bug#41704] [PATCH V2] " Peng Mei Yu
2020-06-09 7:52 ` Ludovic Courtès [this message]
2020-06-14 8:10 ` Peng Mei Yu
2020-06-15 11:08 ` Tobias Geerinckx-Rice via Guix-patches via
2020-06-16 10:58 ` bug#41704: " Peng Mei Yu
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=878sgwoevv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41704@debbugs.gnu.org \
--cc=pengmeiyu@riseup.net \
/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).