[MacPorts] #49343: slime: update to 2.15
MacPorts
noreply at macports.org
Sun Oct 25 06:45:10 PDT 2015
#49343: slime: update to 2.15
---------------------------+------------------------
Reporter: ryandesign@… | Owner: easieste@…
Type: update | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.3.99
Resolution: fixed | Keywords: haspatch
Port: slime |
---------------------------+------------------------
Comment (by ryandesign@…):
Replying to [comment:2 easieste@…]:
> N.b. as far as I understand things, we still need to increment the epoch
field even though we are building to releases.
The only reason why the epoch would need to be increased is if the
MacPorts `vercmp` procedure sees the new version as older than the old
version. For example, if the old version were "20051225" and the new
version were "3.5", then the epoch would need to be increased, because
otherwise MacPorts would see "3.5" as older than "20051225" (because 3 is
less than 20051225) and would not present the port as an outdated port.
That's not the case here: MacPorts has no trouble understanding that
"2.15" is newer than "2.14" (because 15 is greater than 14), so no epoch
increase was necessary. It doesn't hurt anything to increase the epoch in
this case, but there was no reason to do so. (Now that it has been
increased, it cannot be changed back, because the epoch may never be
decreased.)
--
Ticket URL: <https://trac.macports.org/ticket/49343#comment:4>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list