|Commit History - (may be incomplete: see SVNWeb link above for full details)
|This is a slave port. You may also want to view the commits to the master port: security/gpgme|
|28 Mar 2019 05:22:03
Update security/*gpgme* to 1.13.0
|31 Jul 2018 19:05:35
Update security/*gpgme* to 1.11.1
|06 Feb 2018 15:18:23
- Add some magic to support the regression tests in the case where the test
build directory path length exceeds the maximum socket path length.
- Fix shebang in the pinentry test script. At long last, the real reason some
of the tests were failing has been discovered!
- Remove files/patch-tests_gpg_Makefile.in now that the pinentry script is
- Move USES upward.
- Remove workaround for Bug 193528 (fixed in GCC 6+)
- Add full test support.
- QT5 testlib only needed for tests at build time.
- Add DOXYGEN option to install the API documentation. Prevent the
automatic building of the docs if doxygen happens to be installed.
- Bump PORTREVISION due to added options / dependency change
- Add full test support.
- Revert flavor logic move from r460759. The logic being below
<bsd.port.options.mk> was the reason it wasn't previously working.
- Bump PORTREVISION due to added option
|02 Feb 2018 23:30:34
Add a TEST option to toggle in-build testing as it was causing trouble when
the test build directory path length was longer than the maximum socket path
length. A workaround to this problem is noted in the Makefile. 
Prevent the GNUPG1 option and the TEST option from being enabled simultaneously
since the tests mainly revolve around the programs supplied with GnuPG 2.x.
Disable in-build tests for slave ports for now.
Move the flavor logic for the python slave port into the slave port Makefile
as it was not being evaluated correctly when in the master port Makefile.
Reported by: tijl (via private mail) 
|26 Jan 2018 04:02:18
Update to 1.10.0
Simplify python version detection
|05 Apr 2017 20:13:01
Update security/gpgme and friends to 1.9.0 
Add regression test support for master port. Slave port tests are not working
properly and need further investigation.
PR: 218316 (based on) 
Submitted by: gahr 
|26 Nov 2016 23:41:17
Update security/gpgme-* to 1.8.0
In this version, libgpgme-pthread.so has been removed in favor of just
using libgpgme.so as the thread-safe library. PORTREVISION has been
bumped on all ports depending on security/gpgme so that any that may have
linked to -lgpgme-pthread will link to -lgpgme instead.
The Python module provided by security/py-gpgme has been renamed upstream
from pyme3 to gpg. This removes the conflict with security/py-pyme,
although security/py-gpgme is still the direct replacement of that
|18 Oct 2016 19:45:23
- Update security/gpgme to 1.7.0
- Convert to master port and add several slave ports for the newly added
c++, Qt5, and python bindings (security/gpgme-cpp, security/gpgme-qt5,
and security/py-gpgme, respectively)
- The Qt bindings currently provided by deskutils/kdepimlibs4
cannot currently coexist with these new bindings, but will be phased out
in the future
- The python bindings are an updated version of the ones provided by
security/py-pyme and are now being maintained as part of the gpgme project.
They work with both python 2.x and 3.x.