From: Ricardo Wurmus <rekado@elephly.net>
To: "Wiktor Żelazny" <wz@freeshell.de>
Cc: help-guix@gnu.org
Subject: Re: ./pre-inst-env guix build dangerous inside an environment?
Date: Tue, 10 Sep 2019 16:37:03 +0200 [thread overview]
Message-ID: <87a7bcqkts.fsf@elephly.net> (raw)
In-Reply-To: <20190910135802.lorsnzuaofjxifwy@wz.localdomain>
Hi Wiktor,
> While developing my first package definition to be contributed to GNU
> Guix, I followed 14.1 („Building from Git”) and 14.2 („Running
> Guix Before It Is Installed”) of the manual.
>
> 14.1 suggests using a Guix environment via `guix environment guix`. I
> thought it would be even better to do `guix environment --pure guix`,
> and thus obtain some higher level of isolation.
How did you configure Guix? This sounds like perhaps you ran
“./configure” without “--localstatedir=/var”, so that Guix would be
using a different location for its database and thus consider existing
stuff in /gnu to be invalid.
This is not a problem with using an environment. The problem is with
using a Guix that is misconfigured so that it considers /gnu to be
“polluted” and cleans it up according to the fresh database that is
found at the default localstatedir (which is not /var).
--
Ricardo
next prev parent reply other threads:[~2019-09-10 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 13:58 ./pre-inst-env guix build dangerous inside an environment? Wiktor Żelazny
2019-09-10 14:37 ` Ricardo Wurmus [this message]
2019-09-11 16:18 ` Wiktor Żelazny
2019-09-11 19:40 ` Ricardo Wurmus
2019-09-12 15:45 ` Wiktor Żelazny
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=87a7bcqkts.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=wz@freeshell.de \
/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.
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).