On Thu, Jun 19, 2014 at 9:00 AM, Lamar Owen <lo...@pari.edu> wrote: > On 06/18/2014 08:22 PM, Patrick J. LoPresti wrote: >> >> (different topic, different reply) >> >> On Wed, Jun 18, 2014 at 1:16 PM, Lamar Owen <lo...@pari.edu> wrote: >>> >>> The various spec files include the release numbers, and you can track >>> the spec files with their commit IDs. >> >> Could you be more specific? > > > If the spec, patches, and sources are all committed with the same commit ID > for a particular package, you can grab the updated spec file (using the > commit feeds), pull the NEVRA info out of it, and grab the patches and > source (using the commit ID) corresponding to that package's NEVRA. You'll > have to write the tools yourself, or use the tools being written by the > CentOS (and SL) projects.
Pulling the release number" out of the .spec file is actually a matter of RPM configuration interpretation, with aspects like the ".el6" dist value or possibly pre-release source versioning numbers embedded by various means in the actual release number by various optional flags, which may be conditionally set in the .spec file. Take a look at even a simple SPEC file, such as "ntp.spec" ti see how much interpretation it's doing. Relying on the upstream authors to always do the .spec files *last* with new builds is not necessarily fair, and precludes certain type of code merges.
