Install/upgrade compatibility for package version numbers derived from VCS data
Install/upgrade compatibility for package version numbers derived from VCS data
- Subject: Install/upgrade compatibility for package version numbers derived from VCS data
- From: Jeremy Reichman <email@hidden>
- Date: Tue, 30 Mar 2010 10:27:07 -0400
- Thread-topic: Install/upgrade compatibility for package version numbers derived from VCS data
I am interested in the idea of using semantic versioning for packages I'm
deploying. These packages start out from Mercurial repositories, so I can
derive the version number from the semver tags ('v1.0.0') and other data
from the repository to construct Really Specific Version Numbers during my
automated package building process.
In the following case, I use the tag plus the distance from the latest tag
and the short hash of the current revision.
$ hg log -r. --template '{latesttag}+{latesttagdistance}-{node|short}\n' |
sed -e 's/^v//'
1.0.0+1-df34ebfc12c9
Or, I can simply get the semver tag:
$ hg log -r. --template '{latesttag}\n' | sed -e 's/^v//'
1.0.0
My question: In the context of modern PackageMaker packages, would
1.0.0+1-df34ebfc12c9 be interpreted as '1.0.0' by Installer for the purpose
of upgrades?
I ask because I would like to use the longer, more specific version numbers
for my own purposes. However, I don't want to create problems by not using
something that Installer would interpret correctly for upgrades. If problems
were created, I'd settle for the '1.0.0' version numbers.
I want to get around to testing this but I thought I'd ask to see if anyone
already knew. Thanks!
--
Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden