From: Leo Famulari <leo@famulari.name>
To: Matt <matt@excalamus.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Document /homeless-shelter?
Date: Sun, 16 Jan 2022 00:20:49 -0500 [thread overview]
Message-ID: <YeOrMQ+IP7xNQe69@jasmine.lan> (raw)
In-Reply-To: <17e60e604fa.d4b620b31007437.5972832998992327822@excalamus.com>
On Sat, Jan 15, 2022 at 10:19:54PM -0500, Matt wrote:
> As I understand it, $HOME is set to /homeless-shelter during build because that's how Nix does/did it and "there’s no home
> directory in build environments, and perhaps Eelco Dolstra and others back then found that setting ‘HOME’ to a non-existing directory broke
> fewer builds that leaving it unset."
A further rationale is that by using an obviously strange and bogus
value for $HOME, all uses of $HOME in the build container are
highlighted.
Otherwise, if $HOME was unset, build scripts might fall back to
something like $HOME/$USER.
To be clear, the situation is not simply that "there's no home directory
in the build environment". Rather, there must not be a home directory
there. By design, that's a small part of how we ensure that builds are
deterministic.
In all cases, package builds should not be able to depend on the
pathname of a home directory.
> Is this something that should be documented, and if so, where?
It could be documented briefly in the manual section Build Environment
Setup.
next prev parent reply other threads:[~2022-01-16 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 3:19 Document /homeless-shelter? Matt
2022-01-16 5:20 ` Leo Famulari [this message]
2022-01-16 17:38 ` Matt
2022-01-16 18:16 ` Maxime Devos
2022-01-16 18:27 ` Leo Famulari
2022-01-16 18:25 ` Leo Famulari
2022-01-16 18:55 ` Matt
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=YeOrMQ+IP7xNQe69@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=matt@excalamus.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.