guix publish wrt foreign arch

guix publish wrt foreign arch

[Vincent Legoll]

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

-- 
Vincent Legoll

Re: guix publish wrt foreign arch

[Efraim Flashner]

[-- 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 --]

Re: guix publish wrt foreign arch

[Ludovic Courtès]

Hello,

Vincent Legoll <vincent.legoll@gmail.com> skribis:

> 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 ?

To complement what Efraim wrote, ‘guix publish’ itself publishes
anything you have in the store; it does not matter whether these are
x86_64 build results, or aarch64 build results, or anything.

Now, in the setup you mention, you’d need to populate the store with
aarch64 binaries somehow.  This can be done following Efraim’s advice,
for example.

HTH,
Ludo’.