devel/msgpack-c7.0.2

devel/msgpack-c: update to 7.0.2.

devel/msgpack-c{,xx}: Drop maintainership

These need a new maintainer. I kludged things pretty heavily for v6,
and now that v7 is available the whole approach needs to be
reconsidered.

devel/msgpack-c: Update to 6.1.0

devel/msgpack-c: Update to 6.0.2

devel/msgpack-c: Update to 6.0.1

devel/msgpack-c: Fix build

During the 12.4 Sunset pre/post target was removed but CMAKE_BUILD_TYPE
is used in post-install target which can be used only with pre stage.

Approved by:	portmgr (just-fix-it)

*/*: Sunset 12.4-RELEASE/12-STABLE from ports tree

- Remove all references to defunct ARCH arm
- Remove all references to defunct ARCH sparc64
- Remove x11-drivers/xf86-video-sunffb which requires defunct sparc64
  ARCH
- Remove sysutils/afbinit requires defunct sparc64 ARCH
- Remove all references to bktr driver
- Remove all references to defunct FreeBSD_12
- Remove all references to OSVERSION/OSREL corresponding to 12
- Remove conditionals in Mk/Uses/cabal.mk
- Remove sparc reference from Mk/Uses/qt-dist.mk
- Remove BROKEN_sparc64/NOT_FOR_ARCH=sparc64
- Remove BROKEN_FreeBSD_12* from:
- Remove OpenSSL patches from:
- Remove conditional flags for OSVERSION >= 1300000 to fixed flags.
  Also move conditional flags for non sparc64/arm ARCH to fixed flags.

Reviewed by:	brooks, jbeich, rene, salvadore
Differential Revision: https://reviews.freebsd.org/D42068

devel/msgpack-{c,cxx}: Update to 6.0.0

Remember that time two months ago when upstream suddenly changed their
library/cmake/header names and didn't tell anybody, or set a deprecation
period, or make any sort of warning or announcement of any kind? And
then I had to spent a ton of time fixing the breakages?

Well, apparently the msgpack team thought it was such a good idea that
they did it again. With no warning. And no deprecation period. And no
announcements.

I'm over it. I'm not chasing their renames across the tree to satisfy
upstream's two-second attention span. I'm installing links from all the
old names and we can remove them when all the consumers switch to the
new locations, which is in approximately never.

devel/msgpack-c: Update to 5.0.0

The cmake package name has been changed from `msgpack' to `msgpackc'
which might break consumers.

devel/msgpack: Update and split into C and C++ versions

Upstream now provides msgpack as two separate distributions: a C version
with the traditional libmsgpackc.so library, and a header-only C++
version.

devel/msgpack is now devel/msgpack-c and devel/msgpack-cxx, and its
consumers now point to one or both. Note that it is entirely possible
for both to be required. PORTREVISION bump for all consumers.

In my testing, it's not clear that the MSGPACK option in the mariadb
ports actually does anything. I don't think mariadb is actually linking
against msgpack, even before this commit.