[Rpm-maint] [rpm-software-management/rpm] RFE: BuildRequires generator (#104)

[Pavel Raiskup]

On Saturday, February 17, 2018 7:40:53 AM CET Jeff Johnson wrote:
> If -- as this RFE seems to assume -- you are going to limit the implementation
> to "... (Rust, Python, golang) ..." that have alternative non-specfile means
> to specify BuildRequires, then all known rpm build systems will require a
> change to augment the installed files with newly discovered "dynamic"
> BuildRequires.

It is up to the build system whether it is going to implement this;  the worst
case scenario would be to ignore the new format so people won't be allowed to
use the feature "because guidelines".

> Repopulating a buildroot with additional "dynamic" BuildRequires and
> restarting an rpm build either needs to teach rpm how to install additional
> packages as a side effect of parsing, or needs to be handled by depsolvers
> that populate the buildroot (entirely out of scope for the current rpmbuild
> implementation) before rpmbuild is invoked.

Agreed.  IMO rpm should just speficy "script" which prints build-requires to
standard output.  That can/could be:

    %build_requires
    # the script content
    /bin/awk ... do something

or
    %build_requires -f <script-available-in-sources>

or
    %build_requires -s <script-available-in-buildroot>

. this way you don't have to adjust depsolver, only the build-system.





-- 
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/issues/104#issuecomment-366423220
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20180217/537f5e69/attachment.html>