From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28310@debbugs.gnu.org
Subject: bug#28310: guix build -n misses package builds
Date: Sat, 2 Sep 2017 12:04:00 +0200 [thread overview]
Message-ID: <20170902100400.GA1917@jurong> (raw)
In-Reply-To: <87a82exbj7.fsf@gnu.org>
Hello,
On Sat, Sep 02, 2017 at 01:08:12AM +0200, Ludovic Courtès wrote:
> “-n” now implies “--no-grafts” (commit
> fd59105c49965db956fac73c68d8b00d068f5d5c). This was motivated by the
> need to have -n really perform a dry run.
if I understand your answer correctly, then no output with "-n" means that
the ungrafted packages are already available in my store.
> The downside is that with -n we now see only half of the build plan, and
> when we remove -n, we start with the other half of the build plan,
> grafting.
Then this other half would just be grafting, which would not require to
download source and build packages locally.
Or are the built packages the replacements for packages with security
updates, that are grafted upon the existing packages?
Andreas
next prev parent reply other threads:[~2017-09-02 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 19:03 bug#28310: guix build -n misses package builds Andreas Enge
2017-09-01 23:08 ` Ludovic Courtès
2017-09-02 10:04 ` Andreas Enge [this message]
2017-09-02 20:13 ` Ludovic Courtès
2017-09-07 12:42 ` Andreas Enge
2017-09-07 13:24 ` Ludovic Courtès
2020-03-22 11:48 ` 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=20170902100400.GA1917@jurong \
--to=andreas@enge.fr \
--cc=28310@debbugs.gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).