Working with the CVS tag = rpm version idea,
in the case of a bug where a roll-back of a buggy RPM is the best solution.
It's possible to apply two CVS tags to the same revisions of the code.
(I expect you know this.)
So doesn't this mean that a new one could be created simply by tagging
the previous version in CVS with the new tag and cranking the handle on
etics?
e.g. if package foo in dir bar/foo under CVSROOT has an old version
tagged 'foo-00-02-05', then a new version comes out, tagged
'foo-00-02-06' which turns out to have a problem, just do this:
cvs rtag -r foo-00-02-05 foo-00-02-06-01 bar/foo
and produce the rpm for foo-00-02-06-01
Simon
Burke, S (Stephen) wrote:
> Testbed Support for GridPP member institutes
>> [mailto:[log in to unmask]] On Behalf Of Coles, J (Jeremy)
> said:
>> I would need to find out how the build system internally deals with
>> release numbers.
>
> Not at all - the release number is only meaningful at the final step
> when it goes to production. SA3 (including the PPS) deals with
> everything in terms of patches, which are basically collections of rpms
> which implement some coherent change. The rpms are produced by etics,
> and the version number normally corresponds to the cvs tag for the code
> it contains.
>
> Stephen
|