net-im/qxmpp: flavorize for Qt5 and Qt6

net-im/qxmpp-qt5: update to 1.5.5, latest upstream

Release notes at
	https://github.com/qxmpp-project/qxmpp/releases/tag/v1.5.5
just minor pkgconfig and compile fixes.

net-im/qxmpp-qt5: update 1.5.4

net-im/qxmpp-qt5: update to 1.5.3, latest upstream

net-im/qxmpp-qt5: prepare for future net-im/kaidan version

net-im/qxmpp-qt5: update to 1.5.2

net-im/qxmpp-qt5: update to 1.5.1 release (+)

Changelog:	https://github.com/qxmpp-project/qxmpp/releases/tag/v1.5.0
		https://github.com/qxmpp-project/qxmpp/releases/tag/v1.5.1

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.

Clean up some things

- Fix typos
- Remove duplicate variables
- Remove nop variables
- Clean up commented PORTREVISION
- Add missing USES

Reported by:	portscan

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Update net-im/qxmpp-qt5 to latest upstream release

The release notes are here:
	https://github.com/qxmpp-project/qxmpp/releases/tag/v1.4.0
With:
- Qt6 readiness
- Some new features
- Bind IQ errors are now handled properly

Reported by:	portscout

net-im/qxmpp-qt5: update to 1.3.2

This release only contains some little bug-fixes. [1]

Fixes:
    * TransferManager: Fix undefined behaviour when parsing features (#322,
@lichtzeichner)
    * OutgoingServer: Add missing 'to' and 'from' stream attributes (#324,
@Kaffeine)

[1] https://github.com/qxmpp-project/qxmpp/releases/tag/v1.3.2

Update net-im/qxmpp-qt5 to latest upstream release

Release notes at
	https://github.com/qxmpp-project/qxmpp/releases/tag/v1.3.1

The most important change of this release is the fix of CVE-2017-5603.
QXmpp is not vulnerable to roster push attacks (CVE-2016-9928).

Reported by:	portscout
MFH:		2020Q3

Sanitize COMMENT per Section 5.6 of the FreeBSD Porter's Handbook (part 3).

net-im/qxmpp-qt5: update to 1.3.0

Changelog:
	https://github.com/qxmpp-project/qxmpp/releases/tag/v1.3.0

net-im/qxmpp-qt5: update to 1.2.1

net-im/qxmpp-qt5: update to 1.2.0

Changelog:
	https://github.com/qxmpp-project/qxmpp/blob/master/CHANGELOG.md

net-im/qxmpp-qt5: update to 1.1.0

net-im/qxmpp-qt5: update to 1.0.1

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

net-im/qxmpp-qt5: update to 1.0.0

- give maintainership to kde@
- bump consumers

net-im/qxmpp-qt5: unbundle from  net-im/qxmpp (Qt4 deprecation)

Approved by:	portmgr (implicit)

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

Add qxmpp Qt5 slave port needed for polish/kadu update

PR:		214547
Submitted by:	myself
Approved by:	maintainer timeout