Bug#1005206: Split into separate C and C++ API packages

2022-02-15 Thread James McCoy
On Sun, Feb 13, 2022 at 10:35:34PM -0500, nurupo wrote: > It looks like starting with 4.0.0, C and C++ libraries got split in > separate codebases and their version numbers have decoupled -- the > latest msgpack-c release is 4.0.0, while C++ had 4.0.0, 4.0.1, 4.0.2, > 4.0.3 and 4.1.0 releases[1].

Bug#1005206: Split into separate C and C++ API packages

2022-02-13 Thread nurupo
It looks like starting with 4.0.0, C and C++ libraries got split in separate codebases and their version numbers have decoupled -- the latest msgpack-c release is 4.0.0, while C++ had 4.0.0, 4.0.1, 4.0.2, 4.0.3 and 4.1.0 releases[1]. [1] https://github.com/msgpack/msgpack-c/releases

Bug#1005206: Split into separate C and C++ API packages

2022-02-08 Thread nurupo
Package: libmsgpack-dev Version: 3.3.0-4 Severity: wishlist Dear Maintainer, MessagePack provides separate C and C++ APIs. If all you want is the C API, having to install around 150MiB of C++ boost libraries is rather undesired. It would be nice if the package was split into two -- one providing