From: Andreas Enge <andreas@enge.fr>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Install gpg2 as gpg
Date: Wed, 15 Jun 2016 17:54:43 +0200 [thread overview]
Message-ID: <20160615155443.GA6634@solar> (raw)
In-Reply-To: <20160615150258.GC27754@jasmine>
On Wed, Jun 15, 2016 at 11:02:58AM -0400, Leo Famulari wrote:
> All three GnuPG branches (1.4, 2.0, 2.1) are actively maintained. Why
> drop 2.0?
If we start "deprecating" gnupg-1 by calling the gnupg-2 binary "gpg" instead
of "gpg2", then we may as well drop the middle branch. Everything else would
be somewhat confusing, and I do not think we should burden ourselves with
going down the route of patching gnupg-2.0, so that it behaves like gnupg-2.1
in that its binaries look as if they were from gnupg-1 ;-)
Moreover, practically speaking, my impression was that for its ease of use,
there was a point in keeping gnupg-1, why there was less reason for sticking
with 2.0 instead of 2.1.
Andreas
next prev parent reply other threads:[~2016-06-15 15:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 19:55 Install gpg2 as gpg Leo Famulari
2016-06-13 20:24 ` ng0
2016-06-13 21:07 ` Leo Famulari
2016-06-14 7:52 ` Andreas Enge
2016-06-14 12:07 ` Ludovic Courtès
2016-06-14 12:49 ` ng0
2016-06-14 13:37 ` Leo Famulari
2016-06-13 21:42 ` Christopher Allan Webber
2016-06-14 12:09 ` Ludovic Courtès
2016-06-14 13:50 ` Leo Famulari
2016-06-15 12:53 ` Andreas Enge
2016-06-15 15:02 ` Leo Famulari
2016-06-15 15:54 ` Andreas Enge [this message]
2016-06-16 10:56 ` Ludovic Courtès
2016-06-18 1:07 ` Leo Famulari
2016-06-19 14:03 ` Ludovic Courtès
2016-07-24 20:56 ` Ludovic Courtès
2016-07-24 21:10 ` Leo Famulari
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=20160615155443.GA6634@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).