===> The following configuration options are available for qca-qt5-2.3.12:
BOTAN=off: Build with Botan crypto library
GCRYPT=off: Use GNU crypt library instead of OpenSSL
GNUPG=on: GNU Privacy Guard support
LOGGER=off: Simple logger writer
NSS=off: SSL/TLS support via NSS
OPENSSL=on: SSL/TLS support via OpenSSL
PKCS11=off: Smartcard integration
SASL=off: SASL authentication support
SOFTSTORE=off: Simple persistent certificate store
===> Use 'make config' to modify these settings
devel/qca: Update to 2.3.10
Convert TEST option to cmake:testing after 8cb78e3688bf.
Fix build with BOTAN option enabled if security/botan2 is also
installed. [1]
Fixes: 16577400db6b devel/qca: switch to botan3 instead of deprecated botan2
[1]
devel/qca: Update to 2.3.7
Reduce substitutions and improve readability for "private" variables.
Fix TEST option for qt6 flavor.
Changes since 2.3.6:
* OpenSSL3: don't quit if legacy provider is unavailable
devel/qca: update to 2.3.6, latest upstream
From the release announcement email:
A new bugfix release of QCA, the cross-platform cryptography
API for Qt, is out!
* Support botan 3
* Small improvemens to cmake code
* Tweak to which tests are run
Mk/Uses: always use colon for build/run suffix
Most USES use a colon for build/run(/test) suffixes. Change kde.mk,
qt.mk and pyqt.mk to do the same, and update all ports using that.
Document in CHANGES.
PR: 266034
Exp-run by: antoine
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D36349
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Update devel/qca to latest upstream release
QCA is the Qt Cryptographic Architecture - straightforward cross-
platform crypto API. This release has:
* Add macOS framework major version
* qca-gcrypt: Add support for HKDF
* Minimum Qt updated to 5.9
* Fixed compilation with gcc 11
While updating, I have added the patch for LibreSSL compatibility (and
tried to upsteam it). The patch comes via Gentoo and OpenBSD and has
been adjusted by lbartoletti@ and tjlegg@gmail.com and myself,
so I'm filling in something generic-ish in "Obtained from" since it
is collaborative. The PR: entry is for this patch, not for the update
to the recent release.
PR: 248590
Reported by: portscout, tjlegg@gmail.com
Obtained from: Gentoo/OpenBSD
devel/qca: update to 2.3
- qca-2.3 drop support for OSSL<1.1
- copy devel/qca to devel/qca-legacy which is held at the current version
- update devel/qca to 2.3
- Add Uses/qca.mk which handles dependency on either of the ports depending on
the FreeBSD version
Users on FreeBSD11 must therefore change their pkg orign a la:
pkg set -o devel/qca:devel/qca-legacy
PR: 244682
Exp-run by: antoine
Reviewed by: arrowd
Differential Revision: https://reviews.freebsd.org/D24042
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
- Fix build with LibreSSL
Provide RSA_meth_set_{sign,verify} for LibreSSL.
Do not redefine M_ASN1_IA5STRING_new and RSA_F_RSA_EAY_PRIVATE_DECRYPT.
Disable HKDF.
- Add description for BOTAN option
Obtained from: Gentoo
Update devel/qca to latest upstream version 2.2.1
- Mostly for new botan2 support
- Build fixes back-and-forth
The patches are all dropped because they copy what's in git,
or mess around with the test suite to no avail. libressl
is still unsupported (at this point, also because py-cryptography
doesn't build with it).
Add a TEST option and set TEST_TARGET.
This also allows us to get rid of the sed hack in post-patch now that
patch-git_e854f357 handles the dependency on qt5-network correctly.
Replace OpenSSL 1.1.0 with upstream ones
The patches from bug 228902 and added in r481850 are not entirely compatible
with older OpenSSL versions, to the point that the qca-ossl plugin refuses to
load at all on FreeBSD 11.2, for example (see bug 232784 and its duplicates).
Fix it by replacing our patches with backports from upstream the same way
OpenSUSE does it (the OpenSSL 1.1.0 upstream patch was authored by SUSE):
* Revert an upstream commit made only to the 2.1 branch disabling a few ciphers
in the unit tests.
* Backport a change to the master branch that never made it to the 2.1 branch
disabling the ciphers mentioned above as well as a few other ones, so that we
can backport the actual change adding support for OpenSSL 1.1.0 more clealy.
* Backport the actual OpenSSL 1.1.0 support commit, with a few conflicts
(Only the first 15 lines of the commit message are shown above )
Fix Qt5 symbol version scripts to put the catch-all clause first. When
a symbol matches multiple clauses the last one takes precedence. If the
catch-all is last it captures everything. In the case of Qt5 libraries
this caused all symbols to have a Qt_5 label while some should have
Qt_5_PRIVATE_API. This only affects lld because GNU ld always gives the
catch-all lowest priority.
Older versions of Qt5Webengine exported some memory allocation symbols from
the bundled Chromium. Version 5.9 stopped exporting these [1] but the
symbols were kept as weak wrappers for the standard allocation functions to
maintain binary compatibility. [2][3] The problem is that the call to the
standard function in these weak wrappers is only resolved to the standard
function if there's a call to this standard function in other parts of
Qt5Webengine, because only then is there a non-weak symbol that takes
precedence over the weak one. If there's no such non-weak symbol the call
(Only the first 15 lines of the commit message are shown above )
Change cmake default behaviour to outsource.
Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".
I tried to only set insource where explictely needed.
PR: 232038
Exp-run by: antoine
Use regular DEPRECATED and EXPIRATION_DATE variables in an "if FLAVOR" block
instead of flavoring the variables themselves. This caused too much hassle
for Tools/scripts/rmport.
Discussed with: tcberner
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Mark QT4 ports/functionality for removal on 2019-03-15
While here, chase some KDE4 ports and functionality, these are scheduled for
removal on 2018-12-31. Change the default option/flavor to QT5 where applicable
or use alternative toolkits like GTK.
Submitted by: tcberner
Reviewed by: adridg, jhale, rene, tcberner
Approved by: portmgr (implicit, flavor hook)
Differential Revision: https://reviews.freebsd.org/D17741
Fix devel/qca with OpenSSL 1.1.1.
Contains portions extracted from upstream and portions created by
submitter. Upstream bits are marked with their git hash.
PR: 228902
Submitted by: Nathan <ndowens@yahoo.com>
Reported by: brnrd
Replace bsd.qt.mk by Uses/qt.mk and Uses/qt-dist.mk
From now on, ports that depend on Qt4 will have to set
USES= qt:4
USE_QT= foo bar
ports depending on Qt5 will use
USES= qt:5
USE_QT= foo bar
PR: 229225
Exp-run by: antoine
Reviewed by: mat
Approved by: portmgr (antoine)
Differential Revision: -https://reviews.freebsd.org/D15540
Fix COMMENT in devel/qca[-qt5]
devel/qca set COMMENT= thereby overriding the value from devel/qca-qt5.
Set it via ?=.
Approved by: rakuco (mentor)
MFH: 2016Q3
Adjust the SHA0 removal patch.
The upstream fix was still returning "sha0" in all_hash_types() even when SHA0
support is not present. The fix has also been submitted upstream.
PR: 211833
Submitted by: matthew@reztek.cz
MFH: 2016Q3
devel/qca: Fix building without SSLv3 and SHA-0
- Add 2 patches from upstream project
- Fix building when libssl does not have SSLv3
- Fix building when libcrypto does not have SHA-0
- Replace USE_OPENSSL with USES= ssl
- Rework files/patch-libressl with `make makepatch`
Tested with devel/qca and devel/qca-qt5
PR: 210053
Approved by: Maintainer time-out
Obtained from: KDE
Differential Revision: D6885
devel/qca:
- Update to 2.1.1
- Remove patches integrated upstream
- Amend COMMENT
- tarballs are now hosted by KDE Project
devel/qca-qt5:
- Use build switch to avoid conflict with QCA Qt4 instead of patching library
name and install path for headers
- Make port a slave of devel/qca
- Pass maintainership to kde@
PR: 204305
Approved by: pawel
Uses/cmake.mk: Replace CMAKE_ENV with CONFIGURE_ENV.
Instead of defining a variable that is almost always based on CONFIGURE_ENV,
just use CONFIGURE_ENV directly.
This also matches the behavior of other ports that do not use autotools (so
most ports can just worry about CONFIGURE_ENV). Additionally, the fact that
we do not use ?= means we do not have problems if another file in Uses/
needs to set CONFIGURE_ENV (with CMAKE_ENV, the order of the arguments to
USES would matter).
Ports which set CMAKE_ENV have been adjusted accordingly. In most cases,
CMAKE_ENV was just replaced with CONFIGURE_ENV, the exceptions being:
* databases/sqliteman: CMAKE_ENV line removed; setting QMAKESPEC there has
no effect on the build system.
* devel/freeocl: CMAKE_ENV line removed; FREEOCL_CXX_COMPILER is already
retrieved from the CMAKE_CXX_COMPILER variable in the build
system.
* graphics/openimageio: CMAKE_ENV line removed; setting Qt variables there
has no effect on the build system.
Reviewed by: makc
Differential Revision: https://reviews.freebsd.org/D3403
Add upstream patch to remove comma from the last item in an enum.
This fixes the build of at least finance/skrooge on 8.4 and 9.3:
In file included from /usr/local/include/QtCrypto/qca.h:38,
from /usr/local/include/QtCrypto/QtCrypto:1,
from
/wrkdirs/usr/ports/finance/skrooge/work/skrooge-1.10.0/skgbasemodeler/skgservices.cpp:41:
/usr/local/include/QtCrypto/qca_basic.h:598: error: comma at end of enumerator
list
- Update devel/qca to version 2.1.0
- Plugins are no longer available separately so remove security/qca-* and
replace them with options in devel/qca
- Adjust all ports that depended on security/qca-*
- This also fixes the build of the OpenSSL plugin when OpenSSL doesn't
support SSLv2
Approved by: kde (rakuco)
devel/qca:
- Add stage support
- Convert WITH_DEBUG to option
- Remove MAINTAINER_MODE
- Remove now needless stripping in post-install
security/qca-*:
- Convert LIB_DEPENDS to new style
- Add stage support
- Convert WITH_DEBUG to option
- Remove now needless stripping in post-install
- Allow to pass QMAKESPEC to make [1]
- Backport patch from upstream to fix c++ code, it fixes build
with clang/gcc46+
Submitted by: avg (via kde-freebsd ml) [1]
Update to 2.0.2
Changes:
- Bugfix release, forward and backward compatible with 2.0.x
- Fix compatibility with Qt 4.5 when QCA::Initializer appears before QApp
- Don't convert to secure memory when Hash::update(QByteArray) is used
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
QCA is a straightforward and cross-platform crypto API, using Qt datatypes and
conventions.
PR: ports/79289
Submitted by: Vsevolod A. Stakhov <vsevolod@highsecure.ru>
