From: Paul Dufresne <dufresnep@gmail.com>
To: help-guix@gnu.org
Subject: Re: How/When will guix pull stop to compile the 616 files?
Date: Tue, 8 Aug 2017 09:02:06 -0400 [thread overview]
Message-ID: <CAGQ-=q3zpMUO4smZ7GYd=0MjJ=DEWyZZnRgpSOtpEgLrJ6vh7g@mail.gmail.com> (raw)
In-Reply-To: <8760dy8pm8.fsf@gmail.com>
I try to get to the way/vocabulary you use.
It takes 45 mins. on my relatively old dual core to guix-pull (would
say 95% of the time
compiling).
The way I begin to see it, the problem seems that guix-system itself seems to be
considered as latest-drv derivation. I guess I would have prefer that
they would become
616 scheme (all?) derivations.
I believe they would be independant in the sense that compiling
source code to virtual machine does not seems to have dependencies
between the files.
Sadly, I am a lot more of a thinker than a doer.
next prev parent reply other threads:[~2017-08-08 13:02 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 [this message]
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
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='CAGQ-=q3zpMUO4smZ7GYd=0MjJ=DEWyZZnRgpSOtpEgLrJ6vh7g@mail.gmail.com' \
--to=dufresnep@gmail.com \
--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.
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).