summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPanu Matilainen <pmatilai@redhat.com>2019-10-24 12:45:53 +0300
committerPanu Matilainen <pmatilai@redhat.com>2019-11-18 12:46:29 +0200
commit71cd57925afd699b3704d2bc0f2f7fda991070e8 (patch)
treeb15794a28799b072fd3822fb9e303bf4d62e1631
parent6ea40db35224e6c8a66b331f763abb49f321a037 (diff)
downloadrpm-71cd57925afd699b3704d2bc0f2f7fda991070e8.tar.gz
Don't provide rpmlib(DynamicBuildRequires) in source packages
Packages can never provide rpmlib() capabilities, don't pollute the namespace with invalid (if mostly harmless) data. The use-case of identifying whether there are dynamically generated buildrequires in an src.rpm is satisfied by looking for RPMSENSE_FIND_REQUIRES type requires as of commit bee5dc94cf6ee388be821625ba77034bce61c049. (cherry picked from commit ac096e43fc9d09266c0a6f1905821d4e47bc7882)
-rw-r--r--build/build.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/build/build.c b/build/build.c
index 42f9382f5..d6f418793 100644
--- a/build/build.c
+++ b/build/build.c
@@ -209,10 +209,6 @@ static int doBuildRequires(rpmSpec spec, int test)
*packageDependencies(spec->sourcePackage, RPMTAG_REQUIRENAME),
spec->sourcePackage->header);
- parseRCPOT(spec, spec->sourcePackage,
- "rpmlib(DynamicBuildRequires) = 4.15.0-1",
- RPMTAG_PROVIDENAME, 0, RPMSENSE_FIND_PROVIDES | RPMSENSE_RPMLIB,
- addReqProvPkg, NULL);
rc = RPMRC_MISSINGBUILDREQUIRES;
exit: