QGpgme provides a very high level Qt API around GpgMEpp, the GPGME C++
bindings.
There are two general concepts in QGpgME. Data abstraction through
GpgMEpp's Dataprovider interface and the Job pattern.
Data can be provided with QByteArrayDataProvider or QIODeviceDataProvider
which can be constructed from their respective types. This means you can
pass a QFile, QProcess, QString, etc. directly to GPGME.
To provide a stable API / ABI and because of historic reasons in libkleo
(where QGpgME was originally developed as an abstract crypto backend),
QGpgME only provides abstract interfaces as public API while the actual
implementation happens in the private QGpgME prefixed classes.
===> The following configuration options are available for qgpgme-qt6-2.2.0:
DOXYGEN=off: Build documentation with Doxygen
===> Use 'make config' to modify these settings
security/gpgme: Update to 2.0.0
Upstream has split most of the bindings out into separate projects with
this release, so the child ports that were previously providing various
bindings are now autonomous and have new origins. The python bindings
should have been called py-gpg for many years now, since 'gpg' is the
actual module name, so this also corrects that issue.
security/gpgme-cpp -> security/gpgmepp
security/gpgme-qt -> security/qgpgme
security/py-gpgme -> security/py-gpg
gpgmepp and qgpgme have been converted to CMake. py-gpg is now a "fun"
autotools and FreeBSD ports system hybrid. Gpgme, itself, still uses
autotools, but with much less parenting (patching) to do for its
emancipated children.
Adjust several ports to fix API incompatibility with upstream patches
and with some of my own. Adjust all consumers to use the new port
origins of the former child ports.
https://dev.gnupg.org/T7673
