From: ludo@gnu.org (Ludovic Courtès)
To: Alex Vestgaard <birkeroed@protonmail.ch>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: GuixSD installation: binary vs source packages
Date: Mon, 06 Mar 2017 11:59:51 +0100 [thread overview]
Message-ID: <871suavffc.fsf@gnu.org> (raw)
In-Reply-To: <RKjslCs1toc6oiS8cLM8vVhDde45JQ2SLy6p2UrRZkWZQOqyELrSjri_PXeFlYa4HSJfz38Jri0uZHum8cSBDFQzqu__dxcQcV-a9MlucEY=@protonmail.ch> (Alex Vestgaard's message of "Fri, 24 Feb 2017 13:39:23 -0500")
Hello,
Alex Vestgaard <birkeroed@protonmail.ch> skribis:
> 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.
Normally --dry-run should give a good overview of what will be
downloaded and what will be built.
However, in the presence of “grafts”, it may be that additional things
will be downloaded or built without you being notified beforehand.
I consider this a bug but we don’t have an easy fix at this stage.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-03-06 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 18:39 GuixSD installation: binary vs source packages Alex Vestgaard
2017-02-25 2:01 ` 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 [this message]
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
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=871suavffc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=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.
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).