Created attachment 170238 [details]
Two ports use msgpack. Can they cope with the update ? What are the changes from 1.1 to 1.4.1 ?
btw, testbuilds are fine.
The depending ports are:
* textproc/groonga - full text search engine
* editors/neovim - vim fork (currently doesn't build due to bugs that I reported upstream)
From what I see msgpack is expanded and added to.
In both ports this change needs to be made (library is renamed):
libmsgpack.so:devel/msgpack -> libmsgpackc.so:devel/msgpack
(In reply to yuri from comment #4)
Can you point to the bug report for neovim please? Is there a patch available?
Here the neovim bug is fixed and closed on github: https://github.com/neovim/neovim/issues/4750
neovim port doesn't build for me on FreeBSD at all.
neovim is in pre-release now on github.
(In reply to yuri from comment #6)
Thanks, the patch in that bug report fixes it. I can commit that as soon as the msgpack update is committed.
A commit references this bug:
Date: Fri May 27 18:56:53 UTC 2016
New revision: 415958
devel/msgpack: 1.1.0 -> 1.4.2
- dependent ports PORTREVISION bump because name of shared library changed
Submitted by: Yuri Victorovich <firstname.lastname@example.org>
Reviewed by: swills