all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Vestgaard <birkeroed@protonmail.ch>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: GuixSD installation: binary vs source packages
Date: Fri, 24 Feb 2017 13:39:23 -0500	[thread overview]
Message-ID: <RKjslCs1toc6oiS8cLM8vVhDde45JQ2SLy6p2UrRZkWZQOqyELrSjri_PXeFlYa4HSJfz38Jri0uZHum8cSBDFQzqu__dxcQcV-a9MlucEY=@protonmail.ch> (raw)

[-- Attachment #1: Type: text/plain, Size: 801 bytes --]

Hi,

I'm trying to migrate all my machines to GuixSD, which I believe will make some complicated data processing pipelines much easier to deploy and reproduce.

I have one question regarding the installation process, which other people on #guix could not answer. How can I determine what packages will be installed from source and compiled vs just binaries fetched from Hydra?

I tried the --dry-run for guix package -i and guix build, but I didn't find this very informative.

Lengthy compilation took me by surprise twice:

i) When I first started installing GuixSD, Guix got compiled. I expected a binary would be fetched instead.
ii) When installing icecat. I thought in principle there were binary substitutes for all packages in Hydra.

I would appreciate if anyone could clarify these.

Thanks.

[-- Attachment #2: Type: text/html, Size: 1056 bytes --]

             reply	other threads:[~2017-02-24 18:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 18:39 Alex Vestgaard [this message]
2017-02-25  2:01 ` GuixSD installation: binary vs source packages myglc2
2017-02-25 15:52   ` Leo Famulari
2017-02-25 20:12     ` myglc2
2017-02-26  3:23       ` Leo Famulari
2017-03-06 10:59 ` Ludovic Courtès
2017-03-06 16:09   ` dian_cecht
2017-03-07 10:59     ` Ludovic Courtès

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='RKjslCs1toc6oiS8cLM8vVhDde45JQ2SLy6p2UrRZkWZQOqyELrSjri_PXeFlYa4HSJfz38Jri0uZHum8cSBDFQzqu__dxcQcV-a9MlucEY=@protonmail.ch' \
    --to=birkeroed@protonmail.ch \
    --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. 
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.