From: Zhu Zihao <all_but_last@163.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Improve the output of `guix refresh -l`
Date: Fri, 25 Mar 2022 12:50:51 +0800 [thread overview]
Message-ID: <86pmma3a9e.fsf@163.com> (raw)
In-Reply-To: <87o81v9hyz.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
Couldn't agree more :)
Ludovic Courtès <ludo@gnu.org> writes:
> Maxime Devos <maximedevos@telenet.be> skribis:
>
>> Zhu Zihao schreef op do 17-03-2022 om 18:22 [+0800]:
>>> 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.
>>>
>>> What about add an option like `--detail` for `guix refresh -l`?
>>
>> The short option '-l' is a shorthand for the long option
>> '--list-dependents'. It seems to me that '--list-dependents' should
>> actually list the dependents, so I would not do that, otherwise the
>> option name would (by itself) not correspond to its behaviour anymore.
>
> Maybe it could use ‘fill-paragraph’ and
> ‘call-with-paginated-output-port’ so that it’s less annoying?
>
>> Maybe something like a '--count-dependents' option would be nice
>> though.
>
> That too, and/or ‘--direct-dependents’ (sometimes it’s good enough).
>
> Another option would be a ‘guix refresh’ mode that automatically
> rebuilds the updated package and its direct dependents.
>
> Thoughts?
>
> Ludo’.
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2022-03-25 4:52 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 [this message]
2022-04-30 9:40 ` zimoun
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=86pmma3a9e.fsf@163.com \
--to=all_but_last@163.com \
--cc=guix-devel@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).