Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for special system-level %include path #685

Closed

Commits on Apr 26, 2019

  1. Try to continue despite missing %include files on forced spec parse

    On forced spec parse (spec query or --force'd build) we already allow
    sources and patches to be missing. %include differs from sources and
    patches in that a missing include might make the spec unparseable,
    but then we lose nothing by trying, as quite often the spec is parseable
    enough to get at least some info out of it. Doesn't seem any worse
    than allowing build without sources present...
    
    Helps a bit in cases like RhBug:1658292 and RhBug:1547897.
    pmatilai committed Apr 26, 2019
    Configuration menu
    Copy the full SHA
    3151180 View commit details
    Browse the repository at this point in the history
  2. Add support for special system-level %include path

    When %include argument is enclosed in <> (ie similar to C includes),
    look for the file in system-level %_rpmincludedir path instead
    %_sourcedir, and treat these as build-dependencies that get recorded
    in the src.rpm.
    pmatilai committed Apr 26, 2019
    Configuration menu
    Copy the full SHA
    e42563e View commit details
    Browse the repository at this point in the history