From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>, myglc2 <myglc2@gmail.com>
Subject: Re: Rethinking guix pull [was Re: Heads-up: transition to Guile 2.2]
Date: Wed, 17 May 2017 14:45:19 +0200 [thread overview]
Message-ID: <87d1b7zm74.fsf@gnu.org> (raw)
In-Reply-To: <87vap0aj9x.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 16 May 2017 17:55:22 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> I think that a first step towards improving the experience with “guix
> pull” is to build Guix continuously on Hydra and tell “guix pull” to
> download that. Users would no longer have to wait for compilation on
> their local machines, removing a big incentive to go with a git
> checkout. Maybe we should do this first to stop the worst problems,
> buying us a bit more time to implement channels.
That’s probably what we’ll do next. But remember that users will still
have to compute the derivation for that Guix, which in turn should allow
them to get the corresponding substitute, and computing that derivation
is currently relatively costly since you need to compile or interpret a
subset of the Guix code.
Ludo’.
next prev parent reply other threads:[~2017-05-17 12:45 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 16:13 Ready for Guile 2.2! Ludovic Courtès
2017-03-15 20:33 ` Pjotr Prins
2017-03-15 20:41 ` Ludovic Courtès
2017-04-20 12:35 ` Ludovic Courtès
2017-04-20 13:10 ` Andy Wingo
2017-04-20 15:21 ` Maxim Cournoyer
2017-04-21 16:05 ` Joshua Branson
2017-04-22 22:20 ` Ludovic Courtès
2017-04-21 21:03 ` Ludovic Courtès
2017-04-24 1:31 ` Maxim Cournoyer
2017-04-21 21:14 ` Ludovic Courtès
2017-03-31 16:34 ` Ludovic Courtès
2017-04-22 22:34 ` ‘guix pull’ vs. transition to Guile 2.2 Ludovic Courtès
2017-04-23 14:09 ` Jan Nieuwenhuizen
2017-04-27 13:25 ` Ludovic Courtès
2017-05-09 21:22 ` Heads-up: " Ludovic Courtès
2017-05-09 22:26 ` myglc2
2017-05-10 12:05 ` Ludovic Courtès
2017-05-10 17:11 ` myglc2
2017-05-11 0:40 ` myglc2
2017-05-11 8:29 ` Ludovic Courtès
2017-05-11 8:50 ` Vincent Legoll
2017-05-11 20:53 ` Ludovic Courtès
2017-05-11 11:53 ` myglc2
2017-05-11 17:48 ` ng0
2017-05-11 18:17 ` ng0
2017-05-11 20:49 ` Adonay Felipe Nogueira
2017-05-12 8:11 ` Chris Marusich
2017-05-18 12:32 ` ng0
2017-05-14 13:50 ` Pjotr Prins
2017-05-14 15:35 ` Pjotr Prins
2017-05-14 16:13 ` Pjotr Prins
2017-05-14 16:28 ` Jan Nieuwenhuizen
2017-05-14 17:29 ` pjotr.public12
2017-05-14 18:30 ` Creating a reliable bootstrap for building from source Pjotr Prins
2017-05-14 21:32 ` Ludovic Courtès
2017-05-15 1:20 ` David Pirotte
2017-05-15 13:27 ` Ludovic Courtès
2017-05-15 7:35 ` Pjotr Prins
2017-05-15 13:28 ` Ludovic Courtès
2017-05-17 7:47 ` Pjotr Prins
2017-05-19 8:58 ` Ludovic Courtès
2017-05-17 7:52 ` Pjotr Prins
2017-05-14 21:28 ` Heads-up: transition to Guile 2.2 Ludovic Courtès
2017-05-15 7:26 ` Pjotr Prins
2017-05-15 15:48 ` Ludovic Courtès
2017-05-15 20:24 ` Rethinking guix pull [was Re: Heads-up: transition to Guile 2.2] myglc2
2017-05-16 15:55 ` Ricardo Wurmus
2017-05-16 20:56 ` Maxim Cournoyer
2017-05-18 13:54 ` Katherine Cox-Buday
2017-05-18 15:08 ` Ludovic Courtès
2017-05-17 12:45 ` Ludovic Courtès [this message]
2017-05-17 17:54 ` myglc2
2017-05-17 16:06 ` myglc2
2017-05-17 17:46 ` myglc2
2017-05-17 23:45 ` Leo Famulari
2017-05-12 5:41 ` ‘guix pull’ vs. transition to Guile 2.2 Chris Marusich
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=87d1b7zm74.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
--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 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.