Red Hat Bugzilla – Bug 162807
RFE: please add a package tag that can be used to track the configuration management system's 'branch point' used to build the package
Last modified: 2007-11-30 17:11:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 SUSE/1.0.4-1.1
Description of problem:
We find that package name, epoch, version, and revision is the long way around to determining what software is actually in the package; during initial development, version and revision numbers aren't updated often enough, and during later development, tracking something like the subversion repository revision in the rpm revision leads to too-frequent updates.
A new RPM tag that could be used to store information from the CMS system would help us more quickly determine the software deployed on end-user systems without adding signficant 'churn' for updates.
I see no reason why this tag (CVSID? SVNID? CMSID?) should ever be used in determining which package version is higher, so free-form input would be fine by me.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Checked into CVS. The change should be in rpm-4.4.2-0.8 and later. Thanks for the RFE.