From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 46215@debbugs.gnu.org, me@elken.dev
Subject: [bug#46215] [PATCH] Add yadm
Date: Sat, 06 Feb 2021 12:46:11 +0100 [thread overview]
Message-ID: <87y2g1wha4.fsf@nckx> (raw)
In-Reply-To: <78f1ced9e2125994a806383fb1d985d256874a81.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Leo, Ellis,
Leo Prikler 写道：
> I'd like to say "use your best judgement", but you seem to be a
> little
> too fixated on having a minimal package description (and putting
> minimal effort into it).
That's uncalled for. It's certainly not the impression I get.
> For instance, when the package advertises encryption, while it
> is
> technically optional, shipping it without gpg would be a grave
> oversight!
Well, that depends. My own rule of thumb for ‘foo supports
encryption!’ is:
$ gpg
bash: gpg: command not found
$ foo --encrypt
error: whoopsie: BUG in do_foo()+0x4f44!
<16 lines of barftrace>
error: warning: error: No such file or directory. (-ERROR)
$
=> Make gpg an input, and quick.
$ gpg
bash: gpg: command not found
$ foo --encrypt
error: gpg not found, please install it.
$
=> This is totally fine, users who want it know what to do next.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-02-06 11:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 16:47 [bug#46215] [PATCH] Add yadm guix-patches--- via
2021-01-31 17:38 ` Leo Prikler
2021-01-31 20:16 ` guix-patches--- via
2021-01-31 20:36 ` Leo Prikler
2021-02-01 3:44 ` guix-patches--- via
2021-02-01 8:13 ` Leo Prikler
2021-02-01 10:06 ` guix-patches--- via
2021-02-01 11:44 ` Leo Prikler
2021-02-06 10:05 ` Ellis Kenyő via Guix-patches via
2021-02-06 10:48 ` Leo Prikler
2021-02-06 10:58 ` Ellis Kenyő via Guix-patches via
2021-02-06 11:22 ` Leo Prikler
2021-02-06 11:26 ` Ellis Kenyő via Guix-patches via
2021-02-06 11:46 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-02-06 12:41 ` Leo Prikler
2021-02-06 11:30 ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-06 11:43 ` Ellis Kenyő via Guix-patches via
2021-02-06 11:58 ` Leo Prikler
2021-02-06 12:03 ` Tobias Geerinckx-Rice via Guix-patches via
2022-09-09 0:01 ` [bug#46215] [PATCH] gnu: " kiasoc5 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2g1wha4.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=46215@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=me@elken.dev \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.