From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: phodina <phodina@protonmail.com>
Cc: "58903@debbugs.gnu.org" <58903@debbugs.gnu.org>,
"go.wigust@gmail.com" <go.wigust@gmail.com>,
"i@pengmeiyu.com" <i@pengmeiyu.com>
Subject: [bug#58903] Specify the build dir for Nix
Date: Mon, 31 Oct 2022 16:45:30 +0100 [thread overview]
Message-ID: <87sfj4551q.fsf@nckx> (raw)
In-Reply-To: <89-rZ-T-EfdANIf7D2MDU2c9GRrDND1-wshyPcAx6X4dE6AJnN-N9N2r_93XsmOnKcrGShflEKyle5bRxtumYcHvcgwwF_3DZvZUPOSLr70=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
Heyo,
phodina 写道：
> The issue is that there are some packages that fail to build
> even on realtively powerful machine due to resource exhaustion -
> not enough
> RAM.
Yes, this is an issue in Guix as well, e.g., when building disc
images.
> Unfortunately I'm not aware of any other way how to specify I'd
> like to build just this package in other directory (other than
> `/tmp`).
>
> Also is there some other way how Guix handles this issue? I
> might be also used in Nix.
No, Guix uses the exact same mechanism (and possibly code),
inherited directly from Nix.
> (build-dir nix-configuration-build-dir ;string
> (default "/tmp"))
‘directory’. Plz, no unnec. abbrev.
The concept LGTM. Calling it a ‘build directory’ might be
editorialising too much. Does Nix use it for anything else?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-10-31 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 20:45 [bug#58903] [PATCH] gnu: nix: Update to 2.11.1 phodina via Guix-patches via
2022-10-31 15:37 ` [bug#58903] Specify the build dir for Nix phodina via Guix-patches via
2022-10-31 15:45 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-10-31 19:18 ` phodina via Guix-patches via
2022-11-09 22:45 ` [bug#58903] [PATCH] gnu: nix: Update to 2.11.1 Ludovic Courtès
2022-12-13 12:27 ` phodina via Guix-patches via
2022-12-13 16:52 ` bug#58903: " Ludovic Courtès
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=87sfj4551q.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=58903@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
--cc=i@pengmeiyu.com \
--cc=me@tobias.gr \
--cc=phodina@protonmail.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 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).