217815b0af
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
4 lines
210 B
Plaintext
4 lines
210 B
Plaintext
Python bindings for the GpgME library, offering a high-level and curated
|
|
interface, as well as an idiomatic interface implemented as a shim,
|
|
automatically created using SWIG, on top of the low-level interface.
|