Use pyproject.toml's 'version' in build.sh

[phillxnet]

It is proposed that we normalise/centralise on the version defined in pyproject.toml within build.sh when setting the jslibs_version bash variable. This should ease further the procedures required to release rpms: where we synchronise GitHub releases to these version numbers.

[phillxnet]

What we need here is something already available with our existing openSUSE repos akin to:

• stoml: https://github.com/freshautomations/stoml

Or:

• we use Poetry to inform our build.sh of it's given version for this project.
• a simple sed to extract ^version value in a compatible form for a bash variable attribution.

[phillxnet]

Re:

• we use Poetry to inform our build.sh of its given version for this project.

rleap15-4:/opt/rockstor # poetry version
rockstor 5.0.14

Given in build.sh we already use the following before setting jslibs_version:

poetry --version >> poetry-install.txt

to record in poetry-install.txt our live version of Poetry itself. A simple sed/parse or the like of "poetry version"'s output of "rockstor 5.0.14" should be safe to use as a means to set our bash jslibs_version variable a few lines later.

Our most recent poetry-install.txt currently already contains our overall 'rockstor' package version, e.g:

Installing the current project: rockstor (5.0.14)

via our current use in build.sh of:

poetry install -vvv --no-interaction --no-ansi >> poetry-install.txt 2>&1

[phillxnet]

We have the likes of this proposal thus far, poetry version to establish a Bash var, within our Postgres format upgrade script:

Establish Postgres database format upgrade #2780 #2787

rockstor-core/src/rockstor/scripts/db_upgrade.sh

Line 35 in 1ddcf4b

CURRENT_DATA_VERSION=$(cat $DATA_BASEDIR/data/PG_VERSION)

[phillxnet]

Closing as:
Fixed by #2910