On 9/26/13 10:51 AM, Jan Lieskovsky wrote:
Prior being able to provide additional checks for Fedora,
I needed to modify the way how newly generated Fedora rpm
packages will be versioned.
This patch introduces better versioning scheme for Fedora rpm
packages.
Former state:
Generated tarball was based on package name and version only,
therefore the sequence would be (IOW raising "too quickly"):
scap-security-guide-0.1.tar.gz
scap-security-guide-0.2.tar.gz
..
Proposed state:
Generated tarball to be based on package name, version, and
Fedora spec's release, thus the sequence to be:
scap-security-guide-0.1-1.tar.gz - "stable" release
scap-security-guide-0.1-2.rc1.tar.gz \
scap-security-guide-0.1-2.rc2.tar.gz \
.. "devel" releases
scap-security-guide-0.1-2.rc9.tar.gz /
scap-security-guide-0.1-2.tar.gz - another "stable" release,
incorporating changes from rc1 up to rc9
..
Regression testing - proposed patch has been tested and
confirmed as working wrt to the following:
* Fedora tarball, source rpm, and rpm generation,
* Fedora guide, content, checks, validate && eval-common Makefile
rules.
This is an (s)rpm generation / functionality related patch.
No change has been made to existing Fedora content.
This is a very good idea, esp the fedorassgrelease element for
versioning in the spec file.
Ack
(testing this also exposed invalid dates in the current RHEL6 SPEC file
-- bugfix coming shortly)