Generate RPM packages
Summary
In the current state of the build system, the software can be installed locally in the developer environment or system-wide on the computer on which the software has been built (not documented for obvious reasons).
In order to enable deployment, RPM packages should be generated, at least for each release.
What is the expected correct behavior?
RPM packages can be - and are - generated.
Possible fixes
Ideally, the RPM packages are generated following their standard built procedure
-
Produce a SRPM from the latest commit (or any selected commit). It includes a SPEC file as well as the source code. -
Build the RPM based on the SRPM. That should be a trivial task. Note that source code will be rebuilt; that is good since that environment can be completely controlled.