| non port: devel/msgpack-c/Makefile |
|
SVNWeb
|
Number of commits found: 3 |
|
Sat, 4 Mar 2023
|
[ 18:57 Adam Weinberger (adamw)  ]    cb95086
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.
|
|
Tue, 10 Jan 2023
|
[ 17:13 Adam Weinberger (adamw) ] 0d152de
devel/msgpack-c: Update to 5.0.0
The cmake package name has been changed from `msgpack' to `msgpackc'
which might break consumers.
|
|
Sun, 16 Oct 2022
|
[ 21:10 Adam Weinberger (adamw) ] 9e03d99 (Only the first 10 of 28 ports in this commit are shown above.  )
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.
|
Number of commits found: 3 |
As an Amazon Associate I earn from qualifying purchases.