#1466 Per-project mock's `--define 'macro value'` options
Closed: MIGRATED a year ago by nikromen. Opened 3 years ago by praiskup.

This is per IRC discussion; ... :

<pgnd> praiskup: fyi, https://en.opensuse.org/openSUSE:Build_Service_prjconf#Macros ... point #2.  trivial modification of buildroot env.
<praiskup> Ah, ... that's what mock does in 'mock --define 'macro value'
<pgnd> "that's what mock does"  .... now if that config was exposed/availble in COPR/UI ...

What both Koji and Copr require now is to put a macro package with the defines
into the buildroot, and BuildRequire it (or put it into minimal buildroots).

Though the use-case OP had was that the macros actually also affected the source
build (when downloading sources from the internet, before the package is imported
into dist-git). Work-around is to use the %{?macro} variants instead of %{macro}
on all places that affect the source build.

Part of the problem is that we don't allow users to "configure" the buildroot
used for source builds... but it doesn't invalidate the way arount with %? macros.

Metadata Update from @nikromen:
- Issue close_status updated to: MIGRATED
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata