ports/security/gpgme-cpp, branch 2017Q2

Update security/gpgme-* to 1.8.0

2016-11-26T23:41:16Z

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

2016-11-17T13:55:47Z

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

2016-10-19T23:32:55Z

- Check for c++11 compiler for the c++ and Qt bindings

- Update security/gpgme to 1.7.0

2016-10-18T19:45:23Z

- 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