[79340] trunk/dports/net/miniupnpc/Portfile

Ryan Schmidt ryandesign at macports.org
Thu Jun 9 17:44:24 PDT 2011


On Jun 9, 2011, at 16:41, and.damore at macports.org wrote:

> Revision: 79340
>          http://trac.macports.org/changeset/79340
> Author:   and.damore at macports.org
> Date:     2011-06-09 14:41:23 -0700 (Thu, 09 Jun 2011)
> Log Message:
> -----------
> port miniupnpc, set up right compilr, fixed a Makefile issue with resulting library install_name, revision bumped, epoch cleared

The epoch can never be removed from a portfile or decreased. Fixed in r79342.

The epoch is the most significant number for MacPorts when determining if a port is outdated. When MacPorts says that "miniupnpc 1.5_0" is installed, it really means "2_1.5_0" because the epoch is 2. In r79340 you changed it to "0_1.5_1" by removing the epoch line and adding the revision. MacPorts sees "0_1.5_1" as less than "2_1.5_0" so it will not present your update to the user in "port outdated". In r79342 I've put back the epoch line so now it's "2_1.5_1" which is indeed greater than "2_1.5_0" and thus will be presented to the user as an available upgrade.


> use_configure       no
> +build.args-append   CC=${configure.cc}

This does help ensure we're UsingTheRightCompiler, but while you're doing this kind of thing, you may as well also ensure the port is respecting build_arch and, if possible, add a universal variant. Fixed/added in r79343.




More information about the macports-dev mailing list