From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 47989@debbugs.gnu.org
Subject: [bug#47989] [PATCH] channels: Add a #:system argument to channel-instances->manifest.
Date: Mon, 03 May 2021 22:56:31 +0200 [thread overview]
Message-ID: <877dkfv8n4.fsf@gnu.org> (raw)
In-Reply-To: <20210424081402.26742-1-mail@cbaines.net> (Christopher Baines's message of "Sat, 24 Apr 2021 09:14:02 +0100")
Hi,
Christopher Baines <mail@cbaines.net> skribis:
> This allows computing a manifest for a specific system. Previously this was
> possible, but only through changing %current-system, which caused the
> derivation to be computed using that system as well (so computing a derivation
> for aarch64-linux on x86_64-linux would require running aarch64-linux code).
I remember discussing it, but I wonder if I was confused.
I think you can always do the equivalent of (say):
guix time-machine -- build -s armhf-linux hello -d
… where Guix itself is built natively but it then computes a derivation
for a different architecture.
The equivalent code would be roughly:
(let ((inferior (inferior-for-channels …)))
(inferior-package-derivation store
(car (lookup-inferior-packages inferior "hello"))
"armhf-linux"))
Does that make sense?
(You may also want to turn off grafts in the inferior.)
Ludo’.
next prev parent reply other threads:[~2021-05-03 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 8:14 [bug#47989] [PATCH] channels: Add a #:system argument to channel-instances->manifest Christopher Baines
2021-05-03 20:56 ` Ludovic Courtès [this message]
2021-05-03 21:35 ` Christopher Baines
2021-05-04 13:48 ` Ludovic Courtès
2021-05-05 9:28 ` Christopher Baines
2021-05-11 8:48 ` Ludovic Courtès
2021-05-04 13:52 ` Ludovic Courtès
2021-05-05 11:25 ` Christopher Baines
2021-05-05 11:24 ` [bug#47989] [PATCH v2] " Christopher Baines
2021-05-11 8:52 ` [bug#47989] [PATCH] " Ludovic Courtès
2021-05-12 8:52 ` bug#47989: " Christopher Baines
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=877dkfv8n4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=47989@debbugs.gnu.org \
--cc=mail@cbaines.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 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.