Revised rpmbuild instructions.
Added comment in spec file about git release tag naming.
Added mass Fedora 31 rebuild commit history entry.
The reason why the %{name} macro is used twice in the spec file is due to the fact that this git repository includes the project name in release tags which is not that common. If the next series of release tags were simply named with just the version number(1.2.0) then this could get cleaned up in the spec file.
This build process will not work as-is until there is a 1.2.0 release tagged. Normally it would be better to do a release then update the spec file but since the spec file is already at 1.2.0 it would be much uglier if not impossible to revert the spec file to the 1.1.0 version, just food for thought for 1.3.0.
martymac
commented
4 years ago
Revised rpmbuild instructions. Added comment in spec file about git release tag naming. Added mass Fedora 31 rebuild commit history entry.