Hi, I want to tackle this issue again - I really want to package cppzmq as a separate package. Besides the already mentioned reason for not needing to patch downstream build systems, there is also the advantage that you can actually see from apt which version of cppzmq is in Debian. Also, I added pkg-config support. While yes, cppzmq is header only and you don't __need__ a pkg-config lookup, it is much simpler to just add `dependency(cppzmq)` than to check for the headers and depend on libzmq. Additionally I have added an autopkgtest, which is a nice bonus.
Anyway, the change is relatively easy: I already have the packaging done in Salsa [1] and filled an ITP [2]. As I am a DD I can upload and maintain it, the only thing I need from you Laszlo is to remove zmq.hpp and zmq_addon.hpp from the binary package and add cppzmq in Suggests (which should be very low effort). I think it is also a good idea to write a NEWS entry so that users will know about the change, though I think this is not that important if you don't want to put in that much effort. To do the migration, I would first put cppzmq in NEW (after your ok), and after it has been accepted in NEW you would upload the new version of zeromq3. Overall I think the transition will be less painful than patching build systems downstream (and annoying Debian users that write software using the CMake files). [1]: https://salsa.debian.org/debian/cppzmq [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016347
