zmq update

[Clemens Lang]

On Thu, Oct 18, 2012 at 11:26:36AM -0700, Blair Zajac wrote:
> You need to bump the revision on all the ports you updated otherwise
> they won't pick up the new dependency.

https://trac.macports.org/changeset/98866

> Also, you added a zmq port but there was already one in sysutils/zmq
> which you need to manage. It's for 2.2.0 and has nomaintainer, so it
> looks like you could just delete it.

https://trac.macports.org/changeset/98862

On Thu, Oct 18, 2012 at 01:38:53PM -0500, Ryan Schmidt wrote:
> Yes, but changing these ports' library dependencies from zmq to zmq22
> makes them all fail to install now if zmq was already installed. So
> anyone with these ports installed will encounter this problem the next
> time they upgrade or reinstall (which will be immediately if we
> increase the revision, as we should do):

https://trac.macports.org/changeset/98865

> zmq, zmq20 and zmq22 should be made to install files in different
> places and to not conflict with one another.

I've commented in #36576 about this and will be leaving this to the new
maintainer.

> That is what the port naming convention of having a version number
> suffix means. This is in contrast to the foo / foo-devel naming
> convention which means the ports conflict.

The zmq20 and zmq ports previously didn't do this either.

> There is also a zmq20 port. Please decide what category(ies) zmq,
> zmq20 and zmq22 belong in, and put them all in them.

Also in https://trac.macports.org/changeset/98862

> Also, the new zmq port that was added claims to be version 3.2.0 but
> actually installs 3.2.0-rc1. The version line should reflect the
> actual version of software installed.

https://trac.macports.org/changeset/98864

> Both the new zmq port and the new zmq22 port were "svn add"ed to the
> repository. They should have been "svn copy"ed from the existing port,
> so that the four-year-long history of the port is preserved.

Sorry.

-- 
Clemens Lang