On May 4, 2014, at 21:27, ni...@macports.org wrote: > Revision > 119727 > Author > ni...@macports.org > Date > 2014-05-04 19:27:10 -0700 (Sun, 04 May 2014) > Log Message > > OpenBLAS-devel: update to latest commit > Modified Paths > > • trunk/dports/math/OpenBLAS-devel/Portfile > Diff > > Modified: trunk/dports/math/OpenBLAS-devel/Portfile (119726 => 119727) > > --- trunk/dports/math/OpenBLAS-devel/Portfile 2014-05-05 02:26:17 UTC (rev > 119726) > +++ trunk/dports/math/OpenBLAS-devel/Portfile 2014-05-05 02:27:10 UTC (rev > 119727) > @@ -5,7 +5,8 @@ > PortGroup github 1.0 > PortGroup muniversal 1.0 > > -github.setup xianyi OpenBLAS 1140c489c902 > +github.setup xianyi OpenBLAS 020f36f97091 > +revision 1
MacPorts users who had the previous version of this port installed will not be informed of this update via “port outdated” (or “sudo port upgrade outdated”) because: $ ~/macports/users/ryandesign/scripts/vercmp 1140c489c902 020f36f97091 MacPorts considers 1140c489c902 to be greater than 020f36f97091. Increasing the revision has no effect on this. Only increasing the epoch will fix this. And recall that the epoch can never be removed from a port nor decreased. You should pick a version number that in normal updates only increases. A commit hash from a distributed version control system like git is thus not a good choice for the version field. Instead, if the project does not assign version numbers, consider inventing a version number in the YYYYMMDD format. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
