From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22990@debbugs.gnu.org
Subject: bug#22990: Grafts leads to inefficient substitute info retrieval
Date: Sat, 12 Mar 2016 12:23:35 +0300 [thread overview]
Message-ID: <87a8m4123s.fsf@gmail.com> (raw)
In-Reply-To: <8737rxx8gk.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 11 Mar 2016 17:52:59 +0100")
Ludovic Courtès (2016-03-11 19:52 +0300) wrote:
> As of right now (v0.9.0-2007-g66a30a3), ‘graft-derivation’ works either by:
>
> 1. Fetching substitute info about the things being built so that it
> can determine its references, which in turns allows it to determine
> whether they need to be grafted.
>
> 2. Building stuff, as a last resort, so that it can determine its
> references.
I noticed that #1 is happening even with --no-substitutes option. Is it
intended?
I've tried this:
$ guix build --dry-run --no-substitutes mutt
substitute: updating list of substitutes from 'http://hydra.gnu.org'... 100.0%
substitute: updating list of substitutes from 'http://hydra.gnu.org'... 100.0%
substitute: updating list of substitutes from 'http://hydra.gnu.org'... 100.0%
substitute: updating list of substitutes from 'http://hydra.gnu.org'... 100.0%
substitute: updating list of substitutes from 'http://hydra.gnu.org'... 100.0%
The following derivations would be built:
/gnu/store/a2w22xlmfwkgwx4vw11dxc6zrdmww435-mutt-1.5.24.drv
...
--
Alex
next prev parent reply other threads:[~2016-03-12 9:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 16:52 bug#22990: Grafts leads to inefficient substitute info retrieval Ludovic Courtès
2016-03-12 9:23 ` Alex Kost [this message]
2016-03-13 12:11 ` Ludovic Courtès
2016-03-15 18:49 ` Mark H Weaver
2016-03-15 21:50 ` Ludovic Courtès
2016-03-15 8:24 ` Ludovic Courtès
2017-01-08 21:44 ` Ludovic Courtès
2017-01-09 22:55 ` Ludovic Courtès
2017-01-11 9:54 ` Ludovic Courtès
2017-01-11 10:51 ` David Craven
2017-01-11 21:19 ` Ludovic Courtès
2020-03-29 13:41 ` 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=87a8m4123s.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=22990@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).