Commit graph

10 commits

Author SHA1 Message Date
Jason E. Hale
2a5ef47085 Update security/*gpgme* to 1.13.1 2019-09-20 11:36:30 +00:00
Jason E. Hale
b0276a1466 Update security/*gpgme* to 1.13.0
Changes:	https://lists.gnupg.org/pipermail/gnupg-devel/2019-March/034272.html
2019-03-28 05:22:03 +00:00
Jason E. Hale
9434475fd4 Update security/*gpgme* to 1.12.0
Changes:	https://lists.gnupg.org/pipermail/gnupg-devel/2018-October/033977.html
2018-10-12 14:58:53 +00:00
Jason E. Hale
59fe7d00a5 Update security/*gpgme* to 1.11.1
Changes:	https://lists.gnupg.org/pipermail/gnupg-devel/2018-April/033624.html
2018-07-31 19:05:35 +00:00
Jason E. Hale
7f77d3a7df Update to 1.10.0
Simplify python version detection

Changes:	https://lists.gnupg.org/pipermail/gnupg-users/2017-December/059592.html
2018-01-26 04:02:18 +00:00
Jason E. Hale
f9d0b63e5b 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
2017-04-05 20:13:00 +00:00
Jason E. Hale
d32b8fe316 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.
2016-11-26 23:41:16 +00:00
Jason E. Hale
aac4f4ab6b 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
2016-11-17 13:55:47 +00:00
Jason E. Hale
e9c7c9d33d - Update to 1.7.1
- Check for c++11 compiler for the c++ and Qt bindings
2016-10-19 23:32:55 +00:00
Jason E. Hale
4949249b82 - 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
2016-10-18 19:45:23 +00:00