aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorJason E. Hale <jhale@FreeBSD.org>2014-06-22 07:07:42 +0000
committerJason E. Hale <jhale@FreeBSD.org>2014-06-22 07:07:42 +0000
commitdcf209ebbf03953c95ded6ab4e4e33f9848b327c (patch)
treec9d60b813aa64ac4e1bf9f0f20982530b4778f62 /UPDATING
parent1e0521cde78a4beda53da2eca65c0c06af6273b4 (diff)
downloadports-dcf209ebbf03953c95ded6ab4e4e33f9848b327c.tar.gz
ports-dcf209ebbf03953c95ded6ab4e4e33f9848b327c.zip
- Update to 1.5.0
- Simplify MASTER_SITES - Drop signature download and verify target - Strip libraries - Add UPDATING entry documenting behavior change since gpgme now autodetects the gpg binary
Notes
Notes: svn path=/head/; revision=358767
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING14
1 files changed, 14 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 1abd01172477..52b0d552de99 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,20 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20140622:
+ AFFECTS: users of security/gpgme
+ AUTHOR: jhale@FreeBSD.org
+
+ If you have both security/gnupg AND security/gnupg1 installed, gpgme will
+ now automatically detect and use security/gnupg. Specifically, it will
+ search for gpgconf(1) first and use the paths for the binaries provided
+ by it. Failing that, it will search for a binary named "gpg".
+
+ It is no longer possible to specify the location of the gpg binary at
+ buildtime to differentiate between version 1.x and version 2.x. The port
+ options GNUPG1 and GNUPG2 now merely add their respective versions of gnupg
+ as build and runtime dependencies.
+
20140618:
AFFECTS: users of devel/m17n-* textproc/*m17n*
AUTHOR: Nikola Lecic <nikola.lecic@anthesphoria.net>