From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxime Devos <maximedevos@telenet.be>,
Csepp <raingloom@riseup.net>,
guix-devel@gnu.org
Subject: Re: substitute derivation: also substitute grafts?
Date: Sat, 01 Oct 2022 19:29:03 +0200 [thread overview]
Message-ID: <87ill3qwld.fsf@elephly.net> (raw)
In-Reply-To: <87sfk7cx5m.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> The premise was that computing a graft is usually quicker than
> transferring it, which is why they have #:substitutable? #f.
>
> I don’t think it would be reasonable to have a switch to toggle
> #:substitutable? because that would make .drv depend on external
> factors.
If substitutable was merely a hint that a daemon could be free to ignore
it wouldn’t be any worse than downloading a substitute vs building
something locally.
> However, when copying things around, you can still do: ‘guix copy
> /gnu/store/…-xyz’ and that’ll work fine, whether or not it’s a graft.
> But maybe that’s not a satisfying answer for your situation?
“guix copy” only works over SSH, which requires more configuration
(sshd, key exchange, etc) and firewall exceptions. The beauty of
derivation substitution is that it just works without any prior
configuration.
--
Ricardo
next prev parent reply other threads:[~2022-10-01 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 12:58 substitute derivation: also substitute grafts? Ricardo Wurmus
2022-09-15 14:46 ` Csepp
2022-09-15 15:06 ` Maxime Devos
2022-09-15 17:43 ` Csepp
2022-09-15 17:51 ` Maxime Devos
2022-09-19 16:26 ` Josselin Poiret
2022-09-19 16:57 ` Maxime Devos
2022-09-19 22:00 ` Ricardo Wurmus
2022-10-01 16:43 ` Ludovic Courtès
2022-10-01 17:29 ` Ricardo Wurmus [this message]
2022-10-01 18:00 ` Tobias Geerinckx-Rice
2022-10-01 18:27 ` Ricardo Wurmus
2022-10-05 10:03 ` Ludovic Courtès
2022-10-05 11:41 ` zimoun
2022-10-07 22:21 ` Mark H Weaver
2022-10-10 15:32 ` Ludovic Courtès
2022-10-10 15:55 ` zimoun
2022-10-10 17:50 ` Ricardo Wurmus
2022-10-05 12:53 ` Ricardo Wurmus
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=87ill3qwld.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
--cc=raingloom@riseup.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).