unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Install gpg2 as gpg
Date: Sun, 19 Jun 2016 16:03:44 +0200	[thread overview]
Message-ID: <87h9cpz35r.fsf@gnu.org> (raw)
In-Reply-To: <20160618010700.GA28783@jasmine> (Leo Famulari's message of "Fri, 17 Jun 2016 21:07:00 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Thu, Jun 16, 2016 at 12:56:58PM +0200, Ludovic Courtès wrote:
>> Leo Famulari <leo@famulari.name> skribis:
>> 
>> > On Wed, Jun 15, 2016 at 02:53:00PM +0200, Andreas Enge wrote:
>> 
>> [...]
>> 
>> >> Why not just drop gpg-2.0 then?
>> >
>> > All three GnuPG branches (1.4, 2.0, 2.1) are actively maintained. Why
>> > drop 2.0?
>> 
>> +1
>> 
>> Besides, I use 2.0, because for some reason 2.1 has always failed for me
>> (though I never took the time to investigate.)
>> 
>> Anyway, this patch is just about how we name the command.  That the
>> command is called ‘gpg2’ is a well-known annoyance, and Werner
>> recommends not doing that anyway.
>
> Is there a consensus on the way forward? Should we apply this patch to
> gnupg-2.1?

To me it seems the answer is “yes”.  If you want to be sure, please
leave another couple of days before pushing.  :-)

> Is anyone willing to test and maintain patches against gnupg-2.0 (not
> me)?

I can try to do that “eventually”, if nobody beats me at it.

Thanks,
Ludo’.

  reply	other threads:[~2016-06-19 14:03 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
2016-06-16 10:56         ` Ludovic Courtès
2016-06-18  1:07           ` Leo Famulari
2016-06-19 14:03             ` Ludovic Courtès [this message]
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=87h9cpz35r.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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).