From: jgart via Guix-patches via <guix-patches@gnu.org>
To: 60564@debbugs.gnu.org
Cc: Josselin Poiret <dev@jpoiret.xyz>, jgart <jgart@dismail.de>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#60564] [PATCH] scripts: refresh: Add -T option.
Date: Fri, 3 Mar 2023 17:21:36 +0100 [thread overview]
Message-ID: <20230303162135.2864-1-jgart@dismail.de> (raw)
In-Reply-To: <20230105011032.18623-1-jgart@dismail.de>
* doc/guix.texi (Invoking guix refresh): Document the -T option.
* guix/scripts/refresh.scm (%options): Add the -T flag.
---
Hi Josselin and Maxim
> I wonder if this option is common enough to need a dedicated short
> switch?
I would probably use the option more if it had a short option ;()
I think that it is useful. What would be the negative of adding the short option for it?
all best,
jgart
doc/guix.texi | 1 +
guix/scripts/refresh.scm | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 6ff525d0ff..25bbd75f04 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -14327,6 +14327,7 @@ for compatibility with an upgraded @code{flex} package.
@table @code
@item --list-transitive
+@item -T
List all the packages which one or more packages depend upon.
@example
diff --git a/guix/scripts/refresh.scm b/guix/scripts/refresh.scm
index 6498d73c2b..6b633840e0 100644
--- a/guix/scripts/refresh.scm
+++ b/guix/scripts/refresh.scm
@@ -101,7 +101,7 @@ (define %options
(option '(#\r "recursive") #f #f
(lambda (opt name arg result)
(alist-cons 'recursive? #t result)))
- (option '("list-transitive") #f #f
+ (option '(#\T "list-transitive") #f #f
(lambda (opt name arg result)
(alist-cons 'list-transitive? #t result)))
@@ -159,7 +159,7 @@ (define (show-help)
(display (G_ "
-r, --recursive check the PACKAGE and its inputs for upgrades"))
(display (G_ "
- --list-transitive list all the packages that PACKAGE depends on"))
+ -T, --list-transitive list all the packages that PACKAGE depends on"))
(newline)
(display (G_ "
--keyring=FILE use FILE as the keyring of upstream OpenPGP keys"))
--
2.39.1
next prev parent reply other threads:[~2023-03-03 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 1:10 [bug#60564] [PATCH] scripts: refresh: Add -T option jgart via Guix-patches via
2023-01-05 1:35 ` [bug#60564] Probably a lost battle Felix Lechner via Guix-patches via
2023-01-11 19:43 ` [bug#60564] [PATCH] scripts: refresh: Add -T option Maxim Cournoyer
2023-03-03 8:56 ` Josselin Poiret via Guix-patches via
2023-03-03 16:43 ` jgart via Guix-patches via
2023-03-03 16:21 ` jgart via Guix-patches via [this message]
2023-03-04 3:30 ` Maxim Cournoyer
2023-03-04 10:51 ` Josselin Poiret via Guix-patches via
2023-03-21 18:56 ` bug#60564: " Maxim Cournoyer
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=20230303162135.2864-1-jgart@dismail.de \
--to=guix-patches@gnu.org \
--cc=60564@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=jgart@dismail.de \
--cc=maxim.cournoyer@gmail.com \
/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).