security/*gpgme*: Update to 1.24.1

https://dev.gnupg.org/T7440

security/*gpgme*: Update to 1.24.0

Remove security/gpgme-qt-headers. The Qt headers have been folded back
into security/gpgme-qt since they no longer conflict.

https://dev.gnupg.org/T7376

*/*: Chase security/libassuan shlib bump

security/*gpgme*: Update to 1.23.2

https://dev.gnupg.org/T6782

security/*gpgme*: Update to 1.23.0

https://dev.gnupg.org/T6774

security/*gpgme*: Update to 1.22.0

gpgme-qt: Fix COMMENT when FLAVOR is not explicitly set and use just
one PORTREVISION line to avoid confusing bumping tools.

https://dev.gnupg.org/T6668

security/*gpgme*: Update to 1.21.0

Split out the headers shared between the qt5 and qt6 flavors of
security/gpgme-qt to security/gpgme-qt-headers so that they no longer
conflict.

https://dev.gnupg.org/T6585

security/*gpgme*: Update to 1.20.0

https://dev.gnupg.org/T6341 (1.19.0)
https://dev.gnupg.org/T6463 (1.20.0)

security/*gpgme*: Update to 1.18.0

https://dev.gnupg.org/T6128

security/*gpgme*: Update to 1.7.0

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

*: Clean up some things

- Fix typos
- Fix overwritten variables with focus on master/slave ports
- Remove unreferenced variables
- Sort categories
- Remove redundant option descriptions
- Clean up commented PORTREVISION
- Add missing USES

Reported by:	portscan

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

Remove # $FreeBSD$ from Makefiles.

security/*gpgme*: Update to 1.15.1

security/gpgme-cpp: Fix constness

The 1.15.0 release of gpgme-cpp adds a `Signature::operator<` which is missing
a const. In 6a6d2a27648, Signature got an operator< . This is used in
*security/libkleo*, for instance, to sort the signatures for display.

The build failure looks like this (trimmed for brevity, on 13-):

===
/usr/include/c++/v1/algorithm:715:71: error: invalid operands to binary
expression ('const GpgME::UserID::Signature' and 'const
GpgME::UserID::Signature')
    bool operator()(const _T1& __x, const _T1& __y) const {return __x < __y;}

/wrkdirs/usr/ports/security/libkleo/work/libkleo-20.12.0/src/models/
useridlistmodel.cpp:203:14: note: in instantiation of function template
specialization 'std::__1::sort<GpgME::UserID::Signature>' requested here
        std::sort(sigs.begin(), sigs.end());
===

PR:		252283
Submitted by:	adridg

security/*gpgme*: Update to 1.15.0

Update security/*gpgme* to 1.14.0

Update security/*gpgme* to 1.13.1

Update security/*gpgme* to 1.13.0

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

Update security/*gpgme* to 1.12.0

Changes:	https://lists.gnupg.org/pipermail/gnupg-devel/2018-October/033977.html

Update security/*gpgme* to 1.11.1

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

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.

Using ports libc++ on non-leaf ports is problematic, as the requirement
basically flows to all ports that depend on gpgme-{cpp,qt5}. In particular,
sysutils/kf5-kwallet was breaking in FreeBSD 9.x because mismatches between
libc++ and libstdc++ from gcc48 were causing a gpgme symbol not to be found:

backendpersisthandler.cpp:(.text+0xf61): undefined reference to
`GpgME::Context::encrypt(std::vector<GpgME::Key, std::allocator<GpgME::Key> >
const&, GpgME::Data const&, GpgME::Data&, GpgME::Context::EncryptionFlags)'

Switch the build of both ports to lang/gcc on FreeBSD 9 and the system compiler
on FreeBSD 10:
* Use USES:compiler-c++11-lib instead of compiler-c++11-lang, as we do need a
C++11-compatible standard library. This causes the right compiler to be chosen
as described above.
* Set _GLIBCXX_USE_C99 so that gpgme-cpp builds with GCC 4.8 (std::to_string()
is not exposed by default on FreeBSD). Several other ports need to do the same.
* Add a few patches to fix the gpgme-qt5:
** patch-git_b4658f6a1 is a backport from an upstream commit to make the port
   build with GCC 4.8 without errors.
** patch-lang_qt_src_qgpgmeencryptjob.cpp is a local workaround for the
   std::bind() bug mentioned in ports r424451.

PR:		214575
Submitted by:	rakuco

- Update to 1.7.1
- Check for c++11 compiler for the c++ and Qt bindings

- 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