From: Rodrigo Morales <moralesrodrigo1100@gmail.com>
To: help-guix@gnu.org
Subject: Newbie: How to transfer built binaries between Guix systems in the same LAN network?
Date: Sun, 2 Apr 2023 23:38:37 +0000 [thread overview]
Message-ID: <CAGxMbPaf-e2yb5FROPR0m1K8ZH5RdjJVB_V-SZhg-f+PcFg4SA@mail.gmail.com> (raw)
Table of Contents
_________________
1. The context
2. The question
3. Additional information
Newbie: How to transfer built packages from one system from another?
1 The context
=============
I have two systems in the same LAN network: system A and system
B. System A has much better computational resources than system B. I
installed a package in system A, the build stage lasted around 2
hours. I don't want to do the build stage again in system B because
that would require much more time.
I haven't modified any compilation flags and both systems are using
the same architecture, so I suspect that the build stage might yield
the same result (unless my limited knowledge makes me not consider
some aspects that are dependent on each systems' configuration and
make transfer impossible).
I came up with this question when I remembered that the installation
step asked me whether I desired to enable "Substitute server
discovery" (complete prompt shown in the code block below), so I
thought that it might be possible to do the same between two Guix
systems.
--- [Substitute server discovery] ---
By turning this option on, you allow Guix to fetch
subtitutes (pre-built binaries) during installation from
servers discovered on your local area network (LAN) in
addition to the official server. This can increase
download throughput.
There are no security risks: only genuine subtitutes may
be retrieved from these servers. However, eavesdroppers on
your LAN may be able to see what software you are
installing.e
[Enable] [Disable]
2 The question
==============
Is it possible to transfer already pre-built binaries between two Guix
systems that exist in the same LAN network?
3 Additional information
========================
Initially, I assumed this was the default behavior. However, I
successfully installed a package in system A, then I tried to install
the same package in system B, but the build stage still started in
system B.
next reply other threads:[~2023-04-03 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 23:38 Rodrigo Morales [this message]
2023-04-03 0:13 ` Newbie: How to transfer built binaries between Guix systems in the same LAN network? Felix Lechner via
2023-04-06 8:16 ` Simon Tournier
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=CAGxMbPaf-e2yb5FROPR0m1K8ZH5RdjJVB_V-SZhg-f+PcFg4SA@mail.gmail.com \
--to=moralesrodrigo1100@gmail.com \
--cc=help-guix@gnu.org \
/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).