OBS file generation

[guillep]

Put the generation of OBS files into the VM repo to allow for easier updates of dependencies and so on.
OBS files are templates and their meta-data is replaced at build time by CMake using the same version info as for the rest of the packages.

Usage

cmake --build xx --target package

This creates a package obs with the corresponding files to deploy (in addition to the source files).
Still, when pushing the files to obs, the source archive should be named like [PACKAGE_NAME]-[VERSION].tar.gz

Still todo:

• decide the version naming
• automate the final package (containing both obs files and sources with correct naming)

[noha]

For the version naming I think there is two important points: The vm should version its own progress independent of the image. So 10.x.x is fine and with a new leap 11.x.x.
Second is that no matter what version naming there is we need a mapping table that says which vm version can run which image version. This is inevitable and even more reason the vm version should not follow the image

[noha]

btw. good move with this PR 🕺🏼

[guillep]

As for the table, we have this: https://github.com/pharo-project/pharo-vm/wiki/Versions,-Builds-and-Branches which I did a couple of weeks ago.

We can make the next major version pharo-11, that's ok to me

GitHub

Versions, Builds and Branches

This is the VM used by Pharo. Contribute to pharo-project/pharo-vm development by creating an account on GitHub.