[ 21:10 Adam Weinberger (adamw)  ]

• 9e03d9958ec94c454641adc956fd3b40188fc925 MOVED
• 9e03d9958ec94c454641adc956fd3b40188fc925 databases/mariadb103-server/Makefile
• 9e03d9958ec94c454641adc956fd3b40188fc925 databases/mariadb104-server/Makefile
• 9e03d9958ec94c454641adc956fd3b40188fc925 databases/mariadb105-server/Makefile
• 9e03d9958ec94c454641adc956fd3b40188fc925 databases/mariadb106-server/Makefile
• 9e03d9958ec94c454641adc956fd3b40188fc925 devel/Makefile
• 9e03d9958ec94c454641adc956fd3b40188fc925 devel/msgpack-c/Makefile
• 9e03d9958ec94c454641adc956fd3b40188fc925 devel/msgpack-c/distinfo
• 9e03d9958ec94c454641adc956fd3b40188fc925 devel/msgpack-c/pkg-descr
• 9e03d9958ec94c454641adc956fd3b40188fc925 devel/msgpack-c/pkg-plist

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.