From: Marco van Hulten <marco@hulten.org>
To: znavko <znavko@protonmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: guix system reconfigure compiles everything too long
Date: Thu, 20 Sep 2018 10:30:19 +0200 [thread overview]
Message-ID: <20180920103019.2dd8d6a1@elshout2> (raw)
In-Reply-To: <iRqsxlKOkeSCFWSG3xS6GyVIWZSven6_WaN_XuHunomlWnUyUSvHAl4XArSOshe-_LfDIRQr3K9IH5c3RN9As6dL_yyWbUoVYGNK820APWc=@protonmail.com>
Hi—
On Thu, 20 Sep 2018 06:31:27 +0000 znavko wrote:
> Hello! I have been running `guix system reconfigure /etc/config.scm`
> before, and it finished after 1 or 2 hours. Now it is working more
> than 6 hours on Lenovo G50-30. It compiles everything
> http://0x0.st/sxda.png http://0x0.st/sxnm.png even icecat
> http://0x0.st/sx51.png I want it uses binaries, do not need to
> compile sources. Cannot understand, why adding (packages (cons*
> icecat)) produces compilation process of icecat? Please, what is
> wrong?
I could imagine that there is nothing wrong with your system
configuration but that the build servers have not build the latest
versions of the packages yet.
My experience is very mixed in how much needs to be compiled when doing
a system upgrade. In the future I'd like to use a central build server
in my local network (and then I'd probably mount /store over NFS).
—Marco
next prev parent reply other threads:[~2018-09-20 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 6:31 guix system reconfigure compiles everything too long znavko
2018-09-20 8:30 ` Marco van Hulten [this message]
2018-09-20 9:14 ` Pierre Neidhardt
2018-09-20 10:45 ` znavko
2018-09-23 16:20 ` Nils Gillmann
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=20180920103019.2dd8d6a1@elshout2 \
--to=marco@hulten.org \
--cc=help-guix@gnu.org \
--cc=znavko@protonmail.com \
/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).