we had some work on versioning and rewriting version numbers. but on FreeBSD, there is still an issue:
it looks like the 22.214.171.1242... is greater than 126.96.36.199.g...
The underlying issue is a mix of git commits and tagged releases, and
dune subst executing
git describe --always --dirty (which outputs either the tag name for the actual tag, or tag-#commits-#sha for other commits (that are behind a tag)).
A solution in the git world would be to use
git describe --always --dirty --long, but (a) this flexibility is not exposed via
dune subst and (b) sometimes we are building from actual tarballs, not git repos, this may be unavailable.
So, as an alternative, our FreeBSD-repo.sh could enhance the version number accordingly: expecting a tag of the form major.minor.patch, it could detect whether the version is a tag or a commit:
And if a tag is found, append ".0.g0000000".
NOTE: the version is added in the create_package.sh scripts, and there already
sed -e s/-/./g is used -- thus 1.5.0-3-g26b5a59 becomes 188.8.131.52.g26b5a59.
Deleting a branch is permanent. It CANNOT be undone. Continue?