For packages built with Koji, where does the the %{?dist} macro come from?
$ rpm -qf /etc/rpm/macros.dist fedora-release-20-4.noarch
$ cat /etc/rpm/macros.dist # dist macros.
%fedora 20 %dist .fc20 %fc20 1
Something very similar (or the same) should exist for CentOS.
On 02/20/2016 01:02 AM, Shatil Rafiullah wrote:
For packages built with Koji, where does the the %{?dist} macro come from? _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi,
For packages built with Koji, where does the the %{?dist} macro come from?
We have buildsys-macros-<disttag> to enforce a tag if we do not want the default for each distribution.
e.g : http://cbs.centos.org/koji/packageinfo?packageID=6
This package is added in the buildroot during SIG build tag creation phase.
It was agree the SIG could choose a dist tag.
I ma happy to fix it if it's wrong/not wanted somewhere. Let me know.
Hi Thomas,
Thanks for sharing! That may work for me, though for supplying two files an RPM feels heavy-handed. Is this how every SIG includes a custom dist tag in builds?
Where are you placing the buildsys-macros-<disttag> RPM, and how are you including it in Koji?
@Jan, my organization supplies a custom "cantos-release" RPM, so I guess I could just include that as well, since it has the correct macros content.
-
Jan Chaloupka -
Shatil Rafiullah -
Thomas Oulevey