unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: hide more output
Date: Mon, 18 May 2020 00:02:28 +0200	[thread overview]
Message-ID: <87blmmmd8r.fsf@gnu.org> (raw)
In-Reply-To: <87k11pun90.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Wed, 06 May 2020 16:55:07 +0200")

Hi,

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> But can we do even shorter?
>
> - Move the graft information which is somewhat low-level to --verbose=N.
> - Remove the duplicate profile information ("The following
>   derivation..." and "building "/gnu...-profile.drv").
> - If we move the URL to --verbose=N, why not doing the same for the store full path?

Sounds reasonable to me; ‘show-what-to-build’ could take the verbosity
level as an argument.  For ‘guix build’ and ‘guix system build’ we’d
keep the highest verbosity level by default, but for other commands, we
could choose the more silent level.

> $ guix install zile-on-guile vim-full
> The following packages will be installed:
>    zile-on-guile 2.4.14-0.fd09781
>    vim-full      8.2.0411
>
> 9.4 MB will be downloaded:
>  vim-full-8.2.0411  8.9MiB                 7.6MiB/s 00:01 [##################] 100.0%
>  zile-on-guile-2.4.14-0.fd09781  140KiB    1.8MiB/s 00:00 [##################] 100.0%

So in effect, it wouldn’t display anything upfront, only the size of the
stuff downloaded right?  Plus maybe the list of things to build?

Thanks,
Ludo’.


  reply	other threads:[~2020-05-17 22:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 13:38 hide more output Ricardo Wurmus
2020-05-06 14:08 ` Jan Nieuwenhuizen
2020-05-06 14:26   ` zimoun
2020-05-06 14:25 ` Ludovic Courtès
2020-05-06 14:28   ` zimoun
2020-05-06 20:00   ` Bengt Richter
2020-05-06 23:25     ` zimoun
2020-05-06 14:55 ` Pierre Neidhardt
2020-05-17 22:02   ` Ludovic Courtès [this message]
2020-05-18  8:47     ` Pierre Neidhardt
2020-05-18  9:10       ` Jelle Licht
2020-05-18 13:10         ` Katherine Cox-Buday
2020-05-18 13:13           ` Nicolò Balzarotti

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=87blmmmd8r.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).