From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: RFC: Allow gpg and gpg2 for gnupg interaction
Date: Tue, 24 Nov 2020 14:16:04 +0100 [thread overview]
Message-ID: <20201124131604.HJpXXWnUHRjXgJaQBqN4SMrbDit3nYf9A6jJH7WcHnY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-193@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
There's a closed pull request on the mblaze repository
RFC: Allow gpg and gpg2 for gnupg interaction
https://github.com/leahneukirchen/mblaze/pull/193
Description:
The attached commit enables using `gpg` *or* `gpg2` for `gnupg` interaction. The main reason being that Debian installs `gnupg` v2 as `gpg`, and provides an [additional package of just symlinks for gpg2](https://packages.debian.org/buster/gnupg2). I’ll additionally note that, for example, `pass` supports using either so I *believe* compatibility isn’t an issue.
Thoughts?
Thanks,
James
---
Refs 08a46e684855ad8c51c154f843fb1d8527045d33, d9aaac690357d55629b8bbdc885235f68e508783 and 87e5a1b2c308dfa9db85cb3cdd9aa105a5046aed. This purposely doesn’t touch the `GNUmakefile` despite da457c51ee9b0c02c886a7dc641135d3bfa82e63, as you know how your release system works much better than I do ;)
prev parent reply other threads:[~2020-11-24 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 20:31 [PR PATCH] RFC: Allow `gpg` and `gpg2` for `gnupg` interaction JNRowe
2020-11-08 21:59 ` [PR PATCH] [Updated] RFC: Allow gpg and gpg2 for gnupg interaction JNRowe
2020-11-16 18:31 ` JNRowe
2020-11-24 13:15 ` leahneukirchen
2020-11-24 13:16 ` leahneukirchen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201124131604.HJpXXWnUHRjXgJaQBqN4SMrbDit3nYf9A6jJH7WcHnY@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).