summaryrefslogtreecommitdiffstats
path: root/scripts/get-version
AgeCommit message (Collapse)Author
2017-11-06Only considered annotated/signed tags for versionGravatar Dirk Hohndel
This works around confusion with the 'continuous' tag that we now use for the CI AppImage builds. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2015-04-08When building from tar file, check .gitversion to get the correct versionGravatar Dirk Hohndel
Distribution builds on Linux tend to be made from tar files, not from git trees. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2014-10-29Create better version numbering for WindowsGravatar Dirk Hohndel
I don't think this will be a problem for the other OSs, but it needs a bit more testing, especially on the Mac. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2013-02-24Remove more useless quotes.Gravatar Cristian Ionescu-Idbohrn
Signed-off-by: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2013-02-24Use a posix equivalent solution instead of the pattern substitution bashism.Gravatar Cristian Ionescu-Idbohrn
Signed-off-by: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2013-02-24Replace the '==' bashism with the posix equivalent '='.Gravatar Cristian Ionescu-Idbohrn
The quotes are not needed either (nothing to expand there). Signed-off-by: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2013-02-23Expand the version magic even moreGravatar Dirk Hohndel
Someone who is better at shell script writing needs to review this. Here's what it's supposed to do. Create version strings with three or four values for darwin or win, respectively, that we can use as the versions of the bundle or installer. The version that Subsurface reports isn't affected by this. So in a way this is automating something that's mostly cosmetic. If we have a 2 digit version number (like 3.0), do the same the old script did - add just zeroes if we are on a tag, otherwise add the number of commits since the tag (and a last 0 if on win). If we have a 3 digit version numner (like 3.0.1), leave it alone on mac and add either the number of commits since the tag or a zero if we are on the tag on win. Now this can create the same version number for two different versions on darwin: the first commit after 3.0 and the version tagged as 3.0.1 will both get the same number. That's kinda silly but remember - the non-tagged versions aren't supposed to be widely distributed (and the third digit in them should be much larger than anything we'd ever release; we are already on commit 16 since the last tag and hopefully will never release a 3.0.16 as tagged release). And of course the full version as displayed in the About box is always able to tell things apart because of the SHA added at the end if it's a non-tagged version. So why all this magic? The reason we do this is so that during development we are able to create Mac and Windows installers and they get reasonable version numbers, based on the versioning that these vendors suppose. And without manual intervention. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2013-02-16Unified handling of version extraction.Gravatar Cristian Ionescu-Idbohrn
Removed oddly named and ridiculously outdated documentation text (scripts). Created new directory 'scripts'. Added unified version extraction script (scripts/get-version). Yes, it's more shell script code but faster and more maintainable than the sed commands and the swearwords/regexps repeated over and over again. Makefile and packaging/macosx/make-package.sh modified accordingly. I don't do windos neither macos but, AFAICS my tests show, it should be safe. Signed-off-by: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>