Reason:
The outdated port devel/sonarqube has moved to
devel/sonarqube-community to make it clear that it is the community
edition. The log and DB files are still stored in the same location.
The devel/sonar-ant-task port has moved to devel/sonarqube-ant-task
to match the upstream-name. The install location is renamed
accordingly.
At the same time the user/group of the sonarqube port changed from
www:www to sonarqube:sonarqube.
It is expected that nobody was using the 6.2 version from 2016
anymore and no change needs to be done. No analysis was done to check
if the old 6.2 version can be updated in-place to the 8.2 version.
As such if there is still someone using the old 6.2 version, you may
have to delete /var/log/sonarqube and /var/db/sonarqube before
installing the new version.
20200320
New versions of devel/qca stopped supporting OpenSSL < 1.1.
For this reason devel/qca-legacy has been added, which is
held back at an older version until FreeBSD 11 goes EOL.
Ports depending on devel/qca should stop adding direct LIB_DEPENDS
and switch to depending on it via USES=qca.
FreeBSD 11 users might want to run something like
pkg set -o devel/qca:devel/qca-legacy

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

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

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

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

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

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

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)

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)