On Mon, 26 Oct 2020 08:58:22 +0000 Gordon Ball <gor...@chronitis.net> wrote: > On Sun, Oct 25, 2020 at 05:13:52PM +0100, László Böszörményi (GCS) wrote: > > On Fri, Oct 23, 2020 at 4:57 PM Gordon Ball <gor...@chronitis.net> wrote: > > > src:zeromq3 and libzmq3-dev currently embed headers from the separate > > > cppzmq repository. However, the associated cmake files are not included, > > > which means when trying to build downstream projects which use cppzmq > > > and cmake, it's necessary to hack the buildsystem or embed the cmake > > > files from cppzmq. > > These are different projects and should be packaged differently. As > > czmq is packaged by Luca, I think cppzmq should be packaged by him as > > well. But let's hear what he says. > > > > Yes, this seems reasonable. I'm quite willing to see the patch I > prepared as a bit of a nasty hack. > > I prepared standalone packaging for cppzmq a while ago before I realised > that it collided with headers already in libzmq3-dev. The packaging can > be found here: https://salsa.debian.org/chronitis/cppzmq - it's pretty > trivial since it's header only. The package should be more or less ready > to upload if wanted (but probably should be moved out of my salsa namespace). > > However, the maintainer point is a good one. I'm coming at ZMQ in > general as a downstream user and I'm not a domain expert; it would be very > good if the packaging was maintained or co-maintained by someone who > knows the details of ZMQ a bit better. > > > Regards, > > Laszlo/GCS > >
As user of cppzmq, I'd really like to see it packaged in its own package as this makes it easier to track which version of cppzmq is available. This also helps to prevent accidents such as packaging an unreleased version of cppzmq, as it's currently the case at ubuntu. Regards, Lukas