The way I'd do it for now would be: ssh [email protected] guix build mypackage ssh [email protected] guix publish ssh -N -R 8081:localhost:8080 [email protected]& guix build --substitute-urls=http://localhost:8081 mypackage
First, and only once, you need to authorize your machine to use substitute packages from the beefy server ssh [email protected] guix archive --authorize scp [email protected]:/etc/guix/signing-key.pub /tmp/whatever guix archive --authorize < /tmp/whatever Let me know if that works for you. Cheers, Edouard. Christine Lemmer-Webber <[email protected]> writes: > Sometimes I've wanted to offload builds ad-hoc to another server, like > so: > > guix build mypackage [email protected] > > This would offload by ssh'ing into that server and doing the offloading > there, but it's a more explicit user specified location. > > Thoughts? Would this be a worthwhile feature? > > - Christine > > PS: I suppose despite being a more explicit operation, I suppose the > /etc/guix/acl file can't be avoided under our current security model, > because we're still trusting that the remote location is trustworthy > enough to put this build result in our store as the result associated > with this input. One user could, otherwise, screw over all others.
