MessagePack is an efficient binary serialization format, which lets you
exchange data among multiple languages like JSON, except that it's faster and
smaller. Small integers are encoded into a single byte and short strings
require only one extra byte in addition to the strings themselves.
This package provides C++ support. It is header-only and uses boost for all
the heavy lifting.
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-cxx: Create even more links
msgpack has made an absolute mess of things.
For the cmake files, some ports want the new filename in the old
directory name, some want the new name in the new dir, some want the new
name in the old dir, and some want the old name in the new dir.
I'm over it. Let's make even more links (should fix opendht).
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: 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.
