#36576: Fixes for ZMQ ports -------------------------------+--------------------------------- Reporter: merijn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch maintainer Port: zmq zeromq zmq20 | -------------------------------+--------------------------------- Changes (by macsforever2000@…): * keywords: haspatch, maintainer => haspatch maintainer * port: zmq, zeromq, zmq20 => zmq zeromq zmq20 -- Ticket URL: <https://trac.macports.org/ticket/36576#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36576: Fixes for ZMQ ports -----------------------+--------------------------------- Reporter: merijn@… | Owner: and.damore@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch maintainer Port: zmq20 | -----------------------+--------------------------------- Comment (by cal@…): 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. -- Ticket URL: <https://trac.macports.org/ticket/36576#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36576: Fixes for ZMQ ports ------------------------------+--------------------------------- Reporter: merijn@… | Owner: and.damore@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch maintainer Port: zmq20 zmq zmq22 | ------------------------------+--------------------------------- Comment (by jpo@…): Replying to [comment:4 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 -- Ticket URL: <https://trac.macports.org/ticket/36576#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36576: Fixes for ZMQ ports ------------------------------+--------------------------------- Reporter: merijn@… | Owner: and.damore@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch maintainer Port: zmq20 zmq zmq22 | ------------------------------+--------------------------------- Comment (by and.damore@…): 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 [http://lists.macosforge.org/pipermail/macports- dev/2012-February/017744.html getting rid of it]. There's little interest on mongrel2's side to support zmq 3, see [http://librelist.com/browser//mongrel2/2012/1/31/zeromq-3-1-x-support 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. -- Ticket URL: <https://trac.macports.org/ticket/36576#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36576: Fixes for ZMQ ports ------------------------------+--------------------------------- Reporter: merijn@… | Owner: and.damore@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch maintainer Port: zmq20 zmq zmq22 | ------------------------------+--------------------------------- Comment (by merijn@…): Replying to [comment:8 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. -- Ticket URL: <https://trac.macports.org/ticket/36576#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS

#36576: Fixes for ZMQ ports ------------------------------+--------------------------------- Reporter: merijn@… | Owner: and.damore@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: haspatch maintainer Port: zmq20 zmq zmq22 | ------------------------------+--------------------------------- Changes (by cal@…): * status: new => closed * resolution: => fixed Comment: This seems to be fixed. Feel free to re-open if you think this still needs work. -- Ticket URL: <https://trac.macports.org/ticket/36576#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS