Fixes for ZMQ ports

[merijn (Merijn Verstraaten)]

Changes:

• Added devel/zmq22 to provide the legacy ZMQ library previously provided by sysutils/zmq
• Updated and tested* ports depending on the existing zmq port to use zmq22 instead
• Updated the zmq port to the latest officially recommended version (3.2-rc1)
• Moved sysutils/zmq to devel/zmq and dropped sysutils category
• Removed the devel/zeromq duplicate port (had no dependents)
• Removed the sysutils/zmq20 port (no dependents)
• Added myself as maintainer for devel/zmq22 and devel/zmq

• - The still compiled correctly

[merijn (Merijn Verstraaten)]

Unified diff against the root of the ports tree

[jpo@…]

Cc Me!

[neverpanic (Clemens Lang)]

Fixed most of those in r98850. zeromq has previously been removed in r98767.

I'm leaving the decision whether to remove (or rather, transition it so something else) zmq20 to its maintainer, Andrea. I'm reassigning this ticket to him.

[neverpanic (Clemens Lang)]

There were a number of problems with this update. See

• ​http://lists.macosforge.org/pipermail/macports-dev/2012-October/020778.html
• ​http://lists.macosforge.org/pipermail/macports-dev/2012-October/020779.html
• ​http://lists.macosforge.org/pipermail/macports-dev/2012-October/020780.html

I've fixed most of those problems in

• r98862 (deleted duplicate port, moved zmq20 to devel)
• r98863 (fixed port lint warning caused by incorrect category order)
• r98864 (changed the version of the zmq port to 3.2.0-rc1; for the final update to 3.2.0, this requires an epoch increase; added modeline)
• r98865 (added an upgrade path from zmq 2.2 to zmq22 without requiring manual intervention by the user)
• r98866 (bump revision on the ports that had their dependencies changed)

I have not resolved the conflict between zmq and zmq22. Note that zmq20 and zmq have conflicted for a while now, so I'm not even sure this is worth solving.

[jpo@…]

Replying to cal@…:

...

I've fixed most of those problems in

...

• r98864 (changed the version of the zmq port to 3.2.0-rc1; for the final update to 3.2.0, this requires an epoch increase; added modeline) ...

The second release candidate of zeromq 3.2 was released this past weekend.

• Announcement: ​http://lists.zeromq.org/pipermail/zeromq-dev/2012-October/018914.html

• Download: ​http://download.zeromq.org/zeromq-3.2.1-rc2.tar.gz

[jpo@…]

Hi,

I've just created a couple of tickets requesting the update of the zmq and p5-zeromq ports to the latest upstream versions. Both tickets have attached patches [1]:

• zmq: update to 3.2.1-RC2
  ​https://trac.macports.org/ticket/36662

• p5-zeromq: update to 0.23
  ​https://trac.macports.org/ticket/36661
  (depends on zmq22)

/jpo

[1] - the patched ports build correctly in MacOSX 10.6.8.

[anddam (Andrea D'Amore)]

Is there a reason for going with RC rather than a stable version like MacPort's policy?

I'm closing #36662 as duplicate of this ticket.

About the zmq20 IIRC at some point it was the only version mongrel2 built with, and I mean at some point of mongrel2 development. I cannot think of any reason for keeping zmq20, actually I already thought of ​getting rid of it. There's little interest on mongrel2's side to support zmq 3, see ​this thread, but zmq22 should be enough to compile mongrel2, the buildbot at least succeded, my system is failing with any zmq version.

I suggest to add openmaintainer to the ports, this'll streamline minor changes on the port.

[jpo@…]

Replying to and.damore@…:

Is there a reason for going with RC rather than a stable version like MacPort's policy?

Because upstream still hasn't released a final version of ZeroMQ v3. This last release candidate - RC2 - is almost there. See the announcement mail in comment #6 and look at the tarballs names in ​http://download.zeromq.org/ : the 3.0.x and 3.1.x releases were alphas and betas, the 3.2.x are RCs.

I'm closing #36662 as duplicate of this ticket.

You shouldn't. See above.

[merijn (Merijn Verstraaten)]

Replying to and.damore@…:

Is there a reason for going with RC rather than a stable version like MacPort's policy?

RC1 (and now RC2) are the versions recommended by upstream for developing for 3.x, since no existing ports depend on 3.x this seems the best way to go. Although I guess zmq could be replaced with zmq-devel if that's a big issue. Similarly #36662 makes sense for zmq, it's just that RC2 was released after I submitted the original update ticket for ZMQ.

[stromnov (Andrey Stromnov)]

Updated to 3.2.1-RC2 (r99118, actually closes #36662)

Some notes:

• zmq port is no longer openmaintained, so it is harder to keep it in sync with latest zmq versions
• zmq-3.x, especially RC1, is incompatible with zmq-2.x on wire level (PUSH/PULL, PUB/SUB) (partially fixed in RC2)

[stromnov (Andrey Stromnov)]

Cc Me!

[neverpanic (Clemens Lang)]

This seems to be fixed. Feel free to re-open if you think this still needs work.