[Rpm-maint] [rpm-software-management/rpm] Don't insert rpmlib() dependencies for dynamic buildrequires (#878)

Panu Matilainen notifications at github.com
Wed Oct 2 08:34:00 UTC 2019


rpmlib() dependencies are an installability barrier, and dynamic
buildrequires do not qualify: the package cannot be correctly *built*
with older rpm versions, but they will simply fail to parse the spec
due to unknown tag. However rpmlib(DynamicBuildRequires) as it is
injected by rpm 4.15.0 prevents rpm -i (ie unpack) of such an src.rpm,
which is simply wrong as rpm has no problem unpacking it for inspection,
and it's also possible to conditionalize the use of dynamic buildrequires
in a way that makes said src.rpm buildable on the system afterall.

This makes the rpmlib(DynamicBuildRequires) redundant, but we now kinda
have to carry it forever to support unpacking packages created with 4.15.0.

Originally reported in https://pagure.io/copr/copr/issue/1038
You can view, comment on, or merge this pull request online at:

  https://github.com/rpm-software-management/rpm/pull/878

-- Commit Summary --

  * Don't insert rpmlib() dependencies for dynamic buildrequires

-- File Changes --

    M build/build.c (4)
    M build/pack.c (4)

-- Patch Links --

https://github.com/rpm-software-management/rpm/pull/878.patch
https://github.com/rpm-software-management/rpm/pull/878.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/878
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20191002/e7c2d21f/attachment.html>


More information about the Rpm-maint mailing list