[CentOS-devel] git.centos.org rpms with centos in it's release

Sun Aug 10 16:08:32 UTC 2014
Johnny Hughes <johnny at centos.org>

On 08/09/2014 01:14 PM, Markus Falb wrote:
> Hi,
> I tried to match what is installed on a system with what is available at
> git.centos.org.
> for example
> ...
> [centos-release] $ ../../centos-git-common/show_possible_srpms.sh
> centos-release-7-0.1406.el7.centos.2.3.src.rpm
> [centos-release]$ rpm -q centos-release
> centos-release-7-0.1406.el7.centos.2.4.x86_64
> [centos-release]$ rpm -q --qf '%{SOURCERPM}\n' centos-release
> centos-release-7-0.1406.el7.centos.2.4.src.rpm
> ...
> So centos-release-7-0.1406.el7.centos.2.4.src.rpm is not in git!
> Here are all my non matches from quite a minimal system
> name installed-version latest-in-git
> centos-release 7-0.1406.el7.centos.2.4 7-0.1406.el7.centos.2.3
> httpd 2.4.6-18.el7.centos 2.4.6-18.el7_0
> dhcp 4.2.5-27.el7.centos 4.2.5-27.el7
> plymouth 0.8.9-0.10.20140113.el7.centos 0.8.9-0.10.20140113.el7
> cronie 1.4.11-11.el7 1.4.11-13.el7
> yum 3.4.3-118.el7.centos 3.4.3-118.el7
> plymouth 0.8.9-0.10.20140113.el7.centos 0.8.9-0.10.20140113.el7
> kexec-tools 2.0.4-32.el7.centos.2 2.0.4-32.el7_0.2
> chrony 1.29.1-1.el7.centos 1.29.1-1.el7
> basesystem 10.0-7.el7.centos 10.0-7.el7
> libreport 2.1.11-10.el7.centos 2.1.11-10.el7
> tzdata 2014e-1.el7_0 2014e-1.el7
> centos-logos 70.0.6-1.el7.centos 70.0.3-99.el7.centos
> dhcp 4.2.5-27.el7.centos 4.2.5-27.el7
> cronie 1.4.11-11.el7 1.4.11-13.el7
> dhcp 4.2.5-27.el7.centos 4.2.5-27.el7
> plymouth 0.8.9-0.10.20140113.el7.centos 0.8.9-0.10.20140113.el7

CentOS handles the DIST tag as it always has ... if we make changes,
there will be an .el7.centos.  If we rebuild the upstream code exactly,
then we will use their dist tag exactly.  (If this is your question).

Since all DIST tags are dynamic (and the reason for that is because
sometimes Red Hat uses .el7  .. sometimes they use .el7_0, .el7_1, etc).
 Red Hat also does not hard code the DIST tag it is put in at build time
as a variable, but not in the SPEC.

So, the dist tag can be whatever you want, it is dynamic, and passed in
at the time of build (but not hard coded in the SPEC).  That is how Red
Hat releases SPECs.  If XYZ linux wanted to make every DIST tag be
.el7.xyz then they can do that at build time by setting it inside their
rpmmacros at build time.

Red Hat used .el7 for packages in their 7.0 QA release, they use .el7_0
for most updates between 7.0 and 7.1 ... but they use .el7 for FasTrac
builds.  They might, at times, use .el7 for updates (for example, the

So because of this, we will use dynamic DIST tags.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140810/4c539f70/attachment-0007.sig>