From: Jack Hill <jackhill@jackhill.us>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: How/When will guix pull stop to compile the 616 files?
Date: Wed, 9 Aug 2017 09:41:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1708090936300.878@bog.hcoop.net> (raw)
In-Reply-To: <87d185noxu.fsf@elephly.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 702 bytes --]
On Wed, 9 Aug 2017, Ricardo Wurmus wrote:
> Before a substitute can be requested, Guix will have to compute a
> derivation locally. In the case of Guix itself this is rather
> expensive.
>
> Once we have the derivation we can ask substitute servers if they have a
> binary substitute for performing the work the derivation describes.
>
> So, local *computation* cannot be avoided, but local building should be
> avoidable for most packages — here the problem is that hydra isn’t fast
> enough yet. I’ve been preparing an alternative build farm at the
> institute where I work, which will hopefully soon be powerful enough to
> build packages more quickly than our current Hydra does.
Thanks!!
next prev parent reply other threads:[~2017-08-09 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 0:59 How/When will guix pull stop to compile the 616 files? Paul Dufresne
2017-08-08 1:43 ` Paul Dufresne
2017-08-08 7:50 ` Alex Sassmannshausen
2017-08-08 13:02 ` Paul Dufresne
2017-08-08 20:23 ` Ricardo Wurmus
2017-08-08 20:39 ` Jack Hill
2017-08-09 5:43 ` Paul Dufresne
2017-08-09 8:08 ` Ricardo Wurmus
2017-08-09 13:41 ` Jack Hill [this message]
2017-08-13 3:21 ` Quiliro Ordonez Baca
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=alpine.DEB.2.02.1708090936300.878@bog.hcoop.net \
--to=jackhill@jackhill.us \
--cc=help-guix@gnu.org \
--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.
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).