gnupg21: make new port, version 2.1.0

[Schamschula (Marius Schamschula)]

gnupg 2.1.0 has been released (2014-11-06).

Currently, the OS X build fails. The mailing list suggests that a patch may be in git.

[ryandesign (Ryan Carsten Schmidt)]

So you're actually requesting a new port gnupg21 be created, right? That seems best, since according to the ​release announcement:

GnuPG "stable" (2.0) is the current stable version for general use

while:

GnuPG "modern" (2.1) is the latest development with a lot of new features.

Slightly problematically:

You may not install "modern" (2.1) and "stable" (2.0) at the same time.

[Ionic (Mihai Moldovan)]

It's even more complicated than that.

GPG 2.1 and 1.x are incompatible, to the point that the new agent autospawning feature will not work with 1.x. GPG 1.x expects the environment variable GPG_AGENT_INFO to be set, which is deprecated in GPG 2.1, as the socket location is hardcoded and the agent being spawned automatically once a clients tries to connect to it.

This is a known issue and is currently discussed upstream.

I want to hold tight until this comes to some sort of consensus.

Another issue is that the format of secret key storage changed. GPG 2.1 will convert the old format to the new one, but this conversion is one-shot only. Should people use GPG 1.x in parallel, or even switch back to 2.0, new keys will be saved in the "old" format/location and switching back to 2.1 will see those new keys missing.

Really not a nice outlook there, which is why I haven't started working on a new Portfile yet.

[edwin@…]

Since gnupg21 now contains GnuPG 2.1.2, this ticket can be closed, right?

[Ionic (Mihai Moldovan)]

Well... I wanted to leave that open for discussion and also not have GPG 2.1 in the tree for now (not because it's bad per se, but because it's so backwards incompatible.)

What's done is done, though. Adding the original commiter. Closing.