From: "Jonathan Frederickson" <jonathan@terracrypt.net>
To: "Efraim Flashner" <efraim@flashner.co.il>
Cc: "paren--- via" <help-guix@gnu.org>
Subject: Re: Offloading builds asynchronously for use by low-powered machines (or: can you get a home config derivation without building its packages?)
Date: Fri, 27 Dec 2024 17:10:38 -0500 [thread overview]
Message-ID: <30fa9379-7fa4-43b2-84d4-eb4b3a68ea69@app.fastmail.com> (raw)
In-Reply-To: <Z21pLZm5CvXKPKa3@3900XT>
On Thu, Dec 26, 2024, at 9:33 AM, Efraim Flashner wrote:
> I have a pinebook pro and I also have a couple of other aarch64
> machines, and here's what I do:
>
> `guix pull` on my pinebook pro, `guix home build --no-grafts ... -d` and
> `guix system build --no-grafts -d` to get the derivations
>
> Then I'll do `guix copy --to=my-x86_64-machine /gnu/store/...-drv` of
> the two derivations
>
> Then from there I'll build them since I already have offloading setup.
>
> I'll either get substitutes from my main machine, or from there I'll do
> `guix copy --to=pinebookpro $(guix build /gnu/store/...-drv)`, and
> that'll automatically copy the packages to my pinebook pro once it's
> finished building everything.
Oh thanks this was very helpful! I just went and tried running `guix build --no-grafts -d` and it behaved as I expected it to before, returning only the derivation path without building it. I hadn't used `--no-grafts` previously, and that seems to be the crucial difference for this workflow; `guix build -d` without `--no-grafts` seems to attempt a build of (some/all of?) the packages in the derivation.
prev parent reply other threads:[~2024-12-27 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 19:38 Offloading builds asynchronously for use by low-powered machines (or: can you get a home config derivation without building its packages?) Jonathan Frederickson
2024-12-26 14:33 ` Efraim Flashner
2024-12-27 22:10 ` Jonathan Frederickson [this message]
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=30fa9379-7fa4-43b2-84d4-eb4b3a68ea69@app.fastmail.com \
--to=jonathan@terracrypt.net \
--cc=efraim@flashner.co.il \
--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.
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.