Packaging -> Need a tagged version

[SylvainCorlay]

As per discussion on #107, I would like to package cppzmq for conda, it would be very nice to have a tagged version on GitHub, to have a fixed version of the code to refer to.

One thing that would help is that the tag always follow the same pattern and can be completely deduced from the version number. (typically M.m.p).

[JohanMabille]

That would really help with packaging.

[bluca]

Still not 100% sure it makes sense to tag this repository, but if it helps some use cases don't see why not. Pushed v4.2.1 to make it match libzmq

[SylvainCorlay]

Awesome. This is for the reproducible builds of conda-forge.

[SylvainCorlay]

@bluca FYI, cppzmq has been packaged for conda:

conda install cppzmq -c conda-forge

[bluca]

Fantastic, thank you very much for your work!

[SylvainCorlay]

We have also packaged zeromq 4.2.1 with the cmake install files by applying the latests fixes as patches on the top of 4.2.1.

…

On Jan 28, 2017 12:00 PM, "Luca Boccassi" ***@***.***> wrote: Fantastic, thank you very much for your work! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#108 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACSXFiPHoSyi7wCtIPposATyLr3wzC_Oks5rWx_cgaJpZM4Lk4qh> .

[SylvainCorlay]

Quick note on the packaging as we just updated the conda packages for zeromq and cppzmq: cppzmq 4.2.2 works fine with zeromq 4.2.3, which is just a patch release. I think it makes sense for the version numbers of the two packages to be decorrelated and have a clear dependency requirement on zeromq, i.e.

cppzmq 4.2.2 depends on zeromq >=4.2.1,<4.3.0...

or every single patch release of zeromq will require a corresponding cppzmq release, and you won't be able to make releases for cppzmq only.