unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Ricardo Wurmus" <rekado@elephly.net>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>,
	guix-devel@gnu.org, Maxime Devos <maximedevos@telenet.be>,
	Csepp <raingloom@riseup.net>
Subject: Re: substitute derivation: also substitute grafts?
Date: Wed, 05 Oct 2022 13:41:27 +0200	[thread overview]
Message-ID: <86o7uqzee0.fsf@gmail.com> (raw)
In-Reply-To: <87lepusi3g.fsf@gnu.org>

Hi,

On Wed, 05 Oct 2022 at 12:03, Ludovic Courtès <ludo@gnu.org> wrote:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> In my scenario I have two machines, one building stuff the other only
>> substituting.  The serving machine would be the one deciding whether to
>> enforce substitutability or not.
>
> An is it too expensive for that machine to build grafts locally?

Using my old desktop from work, yes the experience is really poor;
especially for some packages where the number of grafts is sometimes
something, e.g., see [1] where grafting were longer than building.

1: <https://yhetil.org/guix/86wnud6db3.fsf@gmail.com>


Cheers,
simon





  reply	other threads:[~2022-10-07  7:56 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
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 [this message]
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=86o7uqzee0.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=me@tobias.gr \
    --cc=raingloom@riseup.net \
    --cc=rekado@elephly.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).