This patch makes a couple of related changes:
- lets you set %{_buildsubdir} as a global to expose it everywhere,
  rather than just specific parts of %prep (%setup and %patch*)
- lets you choose what path is used independently of the unpack
  options in %setup
- allows you to use a different %{_buildsubdir} in different parts of
  the .spec, for instance if you have multiple builds of the same code
  with different compile options
- renames it to %{_buildsubdir} since it's now exposed

Signed-off-by: Peter Jones <pjo...@redhat.com>
You can view, comment on, or merge this pull request online at:

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

-- Commit Summary --

  * Make %{buildsubdir} usable without being a side effect of %setup.

-- File Changes --

    M build/build.c (13)
    M build/files.c (8)
    M build/pack.c (2)
    M build/parsePrep.c (24)
    M build/policies.c (2)
    M build/rpmbuild_internal.h (1)
    M build/spec.c (2)
    M macros.in (4)
    M tests/data/macros.debug (2)

-- Patch Links --

https://github.com/rpm-software-management/rpm/pull/860.patch
https://github.com/rpm-software-management/rpm/pull/860.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/860
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to