From: Maxime Devos <maximedevos@telenet.be>
To: Pāladhammika <paladhammika@protonmail.com>, 53929@debbugs.gnu.org
Subject: [bug#53929] [PATCH] gnu: Add python-onlykey
Date: Sat, 12 Feb 2022 18:53:29 +0100 [thread overview]
Message-ID: <087add2ce88b652930582d187ac9fb6b7328df92.camel@telenet.be> (raw)
In-Reply-To: <INC5bc2y4g2zrFljB3GJRhp96xFBl03g3kqEtB3fiidtdqRM0TbdckmnlE8NY7FSXHUyMg8jAWS4MEeRu5ylrrtEOjR777co1aRgfV1ZHNI=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Pāladhammika via Guix-patches via schreef op do 10-02-2022 om 21:30
[+0000]:
> + (synopsis "OnlyKey client and command-line tool")
> + (description "@code{OnlyKey Python Command-Line Utility} is a
> command line tool
> +targeted towards more advanced users. This can be used for
> configuration and testing.")
This tells me that 'OnlyKey Python Command-Line Utility’ is a CLI
tool with some configuration and testing, and it makes a distinction
between ‘advanced users’ and ... ‘not-advanced users’?
Making a judgement about user's ‘advancedness’ doesn't seem nice,
can the description be factual and descriptive, so potential users
can decide for theirselves whether this package is suitable for them?
Also, this description doesn't tell me anything what this package is
useful for. If I replace ‘Onlykey ... Utility’ by ‘shepherd’, then
this might as well be a description for the 'shepherd' package.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-02-12 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 21:30 [bug#53929] [PATCH] gnu: Add python-onlykey Pāladhammika via Guix-patches via
2022-02-12 17:48 ` Maxime Devos
2022-02-12 22:02 ` Pāladhammika via Guix-patches via
2022-03-06 21:23 ` Ludovic Courtès
2022-04-05 16:09 ` Ludovic Courtès
2022-04-27 21:07 ` Ludovic Courtès
2022-02-12 17:53 ` Maxime Devos [this message]
2022-02-12 22:15 ` Pāladhammika via Guix-patches via
2022-02-12 17:55 ` Maxime Devos
2022-02-12 22:14 ` Pāladhammika via Guix-patches via
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=087add2ce88b652930582d187ac9fb6b7328df92.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53929@debbugs.gnu.org \
--cc=paladhammika@protonmail.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).