unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Zhu Zihao <all_but_last@163.com>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Improve the output of `guix refresh -l`
Date: Sat, 30 Apr 2022 11:40:32 +0200	[thread overview]
Message-ID: <86zgk2oqnj.fsf@gmail.com> (raw)
In-Reply-To: <86v8wcub48.fsf@163.com>

Hi,

On Thu, 17 Mar 2022 at 18:22, Zhu Zihao <all_but_last@163.com> wrote:

> for example, run `guix refresh -l pango`, The terminal prints:
>
> ```
> Building the following 2945 packages would ensure 7521 dependent
> packages are rebuilt: ......<long long package list>
> ```
>
> The package list is too long to read, flood my terminal with package
> names. It will hide the actual rebuilt count, I have to pipe the output
> to less command to make sure I can see it.

Instead of piping to less, I pipe to cut,

    guix refresh -l python-numpy | cut -f1 -d':'

And rebuild, I use:

    guix build $(guix refresh -l python-pytorch | cut -f2 -d':')

or if I need a readable list:

    guix refresh -l python-scipy | cut -f2 -d':' | sed 's/ /\n/g'


> What about add an option like `--detail` for `guix refresh -l`?

I agree that the output of “guix refresh -l” is cumbersome. :-)


Cheers,
simon


      parent reply	other threads:[~2022-04-30  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 10:22 Improve the output of `guix refresh -l` Zhu Zihao
2022-03-17 15:28 ` Maxime Devos
2022-03-24 21:08   ` Ludovic Courtès
2022-03-25  4:50     ` Zhu Zihao
2022-04-30  9:40 ` zimoun [this message]

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=86zgk2oqnj.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=all_but_last@163.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).