*/*: Chase security/libassuan shlib bump

security/*gpgme*: Update to 1.18.0

https://dev.gnupg.org/T6128

security/py-gpgme: Fix build with setuptools 58.0.0+

- Bump PORTREVISION for package change

With hat:	python

security/*gpgme*: Update to 1.7.0

security/py-gpgme: Convert pkg-plist to Python 3.x style

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

security/pygpgme: switch to PYTHON_EXT_SUFFIX

Update security/*gpgme* to 1.13.0

Changes:	https://lists.gnupg.org/pipermail/gnupg-devel/2019-March/034272.html

Update security/*gpgme* to 1.11.1

Changes:	https://lists.gnupg.org/pipermail/gnupg-devel/2018-April/033624.html

security/gpgme:
- 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
  fixed.
- Move USES upward.

security/gpgme-cpp:
- Remove workaround for Bug 193528 (fixed in GCC 6+)

security/gpgme-qt5:
- 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

security/py-gpgme:
- 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

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. [1]

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) [1]

Update to 1.10.0
Simplify python version detection

Changes:	https://lists.gnupg.org/pipermail/gnupg-users/2017-December/059592.html

Update security/gpgme and friends to 1.9.0 [1]
Fix LICENSE
Add regression test support for master port. Slave port tests are not working
properly and need further investigation.

PR:		218316 (based on) [1]
Submitted by:	gahr [1]
Changes:	https://lists.gnupg.org/pipermail/gnupg-users/2017-March/057963.html

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
module.

- 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.

PR:		212886