Jason E. Hale
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
14 lines
459 B
TOML
14 lines
459 B
TOML
Since we don't have a "swig" python package to look for, this breaks the
|
|
build. Swig detection, however, is done locally by the ports system and
|
|
the configure script.
|
|
|
|
--- pyproject.toml.orig 2025-06-17 08:21:23 UTC
|
|
+++ pyproject.toml
|
|
@@ -59,5 +59,5 @@ content-type = "text/plain"
|
|
|
|
[build-system]
|
|
# Minimum requirements for the build system to execute.
|
|
-requires = ["setuptools", "swig"]
|
|
+requires = ["setuptools"]
|
|
build-backend = "setuptools.build_meta"
|