Tag builds done through alr build
with unique build string
#1530
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This may help down the line with reports of people using development versions, to uniquely identify them.
A script is invoked before build to patch in the commit (and an extra flag if the working folder is dirty).
After the build, "_or_later" is added to the build string, so we have a lower bound, but we are not mislead by manual builds that don't trigger the patching (via pure
gprbuild
).So, the new versions would look like
2.0-dev+abcd1234
or2.0-dev+abcd1234_or_later
.Since this triggers rebuilding a bunch of files if using
alr build
to build alr itself, it can be disabled by exportingALR_VERSION_DONT_PATCH
in the environment to avoid those rebuilds during development.