11:29 Adam Weinberger (adamw) 

devel/msgpack-cxx: Update to 6.1.1

    3cdceb9

13:34 Adam Weinberger (adamw) 

devel/msgpack-cxx: Update to 6.1.0

    39f3c32

18:57 Adam Weinberger (adamw) 

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.

    cb95086

17:13 Adam Weinberger (adamw) 

devel/msgpack-cxx: Update to 5.0.0

Note that the cmake package has changed from `msgpack' to `msgpackc-cxx'
which will break some consumers.

    e494d5c

10:51 Adam Weinberger (adamw) 

devel/msgpack-cxx: Update to 4.1.3 (thank you yuri!)

    01b3c28

21:10 Adam Weinberger (adamw) 

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.

    9e03d99