From: ludo@gnu.org (Ludovic Courtès)
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: What’s the weather like?
Date: Mon, 24 Jul 2017 11:07:33 +0200 [thread overview]
Message-ID: <87iniip5ii.fsf@gnu.org> (raw)
In-Reply-To: <CAJ98PDw+2SaeO2F7x1=Zmo_8uOSv_3B-Fg2t4=tuJU+VN7-FYg@mail.gmail.com> (catonano@gmail.com's message of "Sun, 23 Jul 2017 09:25:32 +0200")
Hello!
Catonano <catonano@gmail.com> skribis:
> First: having never being involved with binaries publishing I don't know
> what you mean with
> "if the server uses
> ‘guix publish --cache’"
The ‘--cache’ option instructs ‘guix publish’ to maintain a cache of the
archives it publishes (“nars”):
https://www.gnu.org/software/guix/manual/html_node/Invoking-guix-publish.html
> or with
>
> "We can add multiple -s flags"
One can run “guix weather -s x86_64-linux -s armhf-linux” to get results
for both ARM and x86_64.
> Having said that, I think it would be interesting to have the percentage of
> missing binaries for a specific operation rathher than for the whole server
>
> For example, if I want to reconfigure my system or if I want to create a VM
> image, how many binaries are missing in order to do that ?
You can always use “--dry-run”, which shows a list of what would be
built/downloaded. The possibly long lists it returns are not as easy to
read as we’d like, though.
Ludo’.
next prev parent reply other threads:[~2017-07-24 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 15:13 What’s the weather like? Ludovic Courtès
2017-07-23 7:25 ` Catonano
2017-07-24 9:07 ` Ludovic Courtès [this message]
2017-07-24 11:17 ` Vincent Legoll
2017-07-24 13:15 ` Ludovic Courtès
2017-07-24 14:48 ` Vincent Legoll
2017-07-23 7:58 ` Ricardo Wurmus
2017-07-23 10:26 ` Ricardo Wurmus
2017-07-23 11:02 ` Ricardo Wurmus
2017-07-25 10:26 ` Ludovic Courtès
2017-07-26 20:22 ` Alex Kost
2017-07-27 9:06 ` Ludovic Courtès
2017-07-27 11:39 ` Ricardo Wurmus
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=87iniip5ii.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=catonano@gmail.com \
--cc=guix-devel@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).