all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix publish wrt foreign arch
Date: Wed, 18 Mar 2020 09:42:44 +0200	[thread overview]
Message-ID: <20200318074244.GO927@E5400> (raw)
In-Reply-To: <CAEwRq=qfpSXMXuYE4y2W=Yq71-ZCa2G_iXFJwQAJe0WvQnFE1Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

On Tue, Mar 17, 2020 at 03:25:24PM +0100, Vincent Legoll wrote:
> Hello,
> 
> I'm wondering if guix publish (or something else) could act as local
> network substitute cache for foreign arch ?
> 
> I.e. using a x86_64 host as a substitute server for, say, arm64 hosts...
> 
> Would it only serve as a local cache of source downloads ?
> 
> How would I setup that ?
> 
> Thanks

I would go about it by running 'guix build --no-grafts foo
--system=aarch64-linux'. Depending on if your x86_64 box is setup to
build aarch64 binaries or not and if there are substitutes for those
packages or not it'll download substitutes or sources and try to build
it or fail. But in either case your x86_64 machine will serve up the
substitutes it has, which in this case would include at least some
aarch64 packages.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-03-18  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 14:25 guix publish wrt foreign arch Vincent Legoll
2020-03-18  7:42 ` Efraim Flashner [this message]
2020-03-18 14:56 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200318074244.GO927@E5400 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=vincent.legoll@gmail.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.