#458 Increment the RPM release number each time it is built

[Anthony Shortland]

It seems the RPM release number is hard-coded to "1" for each version of the ControlTier RPMs ... it should really be incremented with each build to that the packages can be upgraded using the "rpm -U" command.

[root@bomapp pkgs]# rpm -qi ctier-client
Name : ctier-client Relocations: /opt/ctier
Version : 3.4.10 Vendor: ControlTier, Inc.
Release : 1 Build Date: Sat 09 Jan 2010 04:27:58 PM PST
Install Date: Tue 19 Jan 2010 09:28:47 AM PST Build Host: localhost.localdomain
Group : ControlTier Source RPM: ctier-client-3.4.10-1.src.rpm
Size : 80804078 License: Apache
Signature : (none)
Packager : ControlTier <info@controltier.com>
URL : http://wiki.controltier.org
Summary : Client for the ControlTier automation framework
Description :
ControlTier Client

[Anthony Shortland]

Tool the liberty of assigning this to you, Greg.

[Anthony Shortland]

In fact ... how about using the build number as the release number? Sweet

[Greg Schueler]

Committed revision 10105: Update buildall.sh: use a release number stored in version.properties as rpm release number, add -release option to buildall.sh to increment the number and commit it to subversion, change the seedsvn export to be a checkout/update, and add revert step to -clean option for seedsvn dir. Update build jobs. Rename newrelease.sh to newversion.sh. Update newversion.sh script to reset the release number on new version.

[Greg Schueler]

Committed revision 10107: better regex for replacing Release token in spec file templates