[MacPorts] #28811: splash @1.14.1 new portfile
MacPorts
noreply at macports.org
Fri Mar 18 00:04:39 PDT 2011
#28811: splash @1.14.1 new portfile
-------------------------------------+--------------------------------------
Reporter: daniel.price@… | Owner: macports-tickets@…
Type: submission | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: maintainer | Port: splash
-------------------------------------+--------------------------------------
Comment(by ryandesign@…):
Replying to [comment:2 daniel.price@…]:
> One questions on removing the epoch: My understanding of this is that if
(say) I update the version to 2.0, it would come "before" 1.14.1, so I
need an epoch there to get the ordering correct. So is the right thing to
do just to add an epoch field when I do eventually release 2.0?
MacPorts definitely knows that "2.0" comes after "1.14.1" as you would
expect, so you do not need an epoch for that. You only need to add an
epoch when version numbers ever seem to go "backwards" when considered
according to the normal dotted-decimal numbering scheme used by most
software. Examples:
* when upgrading from a release candidate to a final version (e.g. "2.0"
should be greater than "2.0-rc2" but MacPorts doesn't think so, so you
need to increase the epoch)
* when upgrading software that uses floating-point version numbering,
like Perl modules (e.g. "1.2" should be greater than "1.14")
* when upgrading software that uses DCVS revision hashes as version
numbers (e.g. perhaps "6b786dae" should be greater than "8e81aee7")
--
Ticket URL: <https://trac.macports.org/ticket/28811#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list