Tarballs have two main advantages for releases:
- they contain translations
- they do not require a Bitbake roundtrip to the git server, which is
important of sstate caching and reproducible builds (when using a tag
instead of a hash, Bitbake resolves the tag on each build)
The current script version expects that the sha256 values are checked
against the respective release.
I am actully not sure why, but looking at the bitbake environment
trace, the weak assignment operator leads to SUMMARY and
consequently also DESCRIPTION to be set to a default value instead
of the preset value.
The change was performed as follows:
- it was checked that the COPYING.MIT license was present with the
initial commit and such each contributor was awere of the license
- mail was around to all previous contributors to check this assumption
(mail was not replied by Hannah and Sebastian); every reply was a
confirmation of the assumed MIT licensing
- all copyright information were recovered from the respective Git
commits
- reuse lint was to used to check the REUSE conformance
