Now there is no convenient way to set the version number
in the required format if we build SeaBIOS from the repository.
It is proposed first of all to get the version number from
the .version file if it exists, if it is absent, from git.
This approach will allow you to safely specify the version
manually and will not affect existing builds.

Alexey Kirillov (1):
  build: increase .version priority over git

 scripts/buildversion.py | 19 ++++++++++++-------
 1 file changed, 12 insertions(+), 7 deletions(-)

-- 
2.17.1
_______________________________________________
SeaBIOS mailing list -- seabios@seabios.org
To unsubscribe send an email to seabios-leave@seabios.org

  Hi,

> This approach will allow you to safely specify the version
> manually and will not affect existing builds.

We don't want an easy way to override the version.  It's useful
to have the exact version in the logs for bug reports etc.

We might change the way the version string is built though.
For starters scripts/tarball.sh and scripts/buildversion.py
are not consistent, it makes sense to fix that.  For example
scripts/tarball.sh detects that a release tag is checked out
and generated a shorter version string without git hash
included then.

So, what exactly do you need?

cheers,
  Gerd
_______________________________________________
SeaBIOS mailing list -- seabios@seabios.org
To unsubscribe send an email to seabios-leave@seabios.org