For git sources, let's use the output of git describe instead; using only a ref: and a comment to know the version integrated is too fragile
Context
Using only a ref and a comment to know what version we are integrating is extremely fragile. We (I) have done the mistake at least 2 times;
Let's use machines (git itself) to be sure the SHA we want to integrate is actually the version we want to integrate
Description
git track
will automatically update the ref:
to use the output of git describe
in bst master; use that or the git_tag
plugin
Example of the propossed change:
sources:
- kind: git_tag
url: https://gitlab.freedesktop.org/mesa/mesa.git
- ref: d219361b4226944835959676d1721b2a9d29da72 # mesa-18.2.3
+ ref: mesa-18.2.3-0-gd219361b4226944835959676d1721b2a9d29da72
- kind: patch
path: patches/mesa-Fix-linkage-against-shared-glapi.patch
Acceptance Criteria
All the git elements use the output of git describe
on the ref:
Edited by Javier Jardón