[scl.org] Setting SCL RPM build options in COPR?

Nick Coghlan ncoghlan at redhat.com
Tue Sep 19 08:10:21 UTC 2017

On Tue, Sep 19, 2017 at 5:31 PM, Petr Kubat <pkubat at redhat.com> wrote:
> On 09/19/2017 08:16 AM, Nick Coghlan wrote:
>> I couldn't find anything in sclorg-distgit
>> that actually *sets* them for the rh-python35 case.
>> https://github.com/sclorg-distgit/rh-python35/blob/sig-sclo7-rh-python35-rh/macros.additional.rh-python35
>> has the comment "the @scl@* macros are defined in
>> macros.python3.python33 in python33-python-devel"
>> That's presumably referring to
>> https://github.com/sclorg-distgit/python/blob/sig-sclo7-rh-python35-rh/macros.python3,
>> which still doesn't *set* "@scl@" or "@vendorscl@", it assumes they're
>> set somewhere else.
> The "@scl@" and "@vendorscl@" symbols are replaced by proper values during
> the build of the metapackage [1], and the resulting macros get installed
> using the *-build sub-package [2] as Honza mentioned.
> [1]
> https://github.com/sclorg-distgit/rh-python35/blob/sig-sclo7-rh-python35-rh/rh-python35.spec#L113
> [2]
> https://github.com/sclorg-distgit/rh-python35/blob/sig-sclo7-rh-python35-rh/rh-python35.spec#L137

Ah, thanks - that's the step I was missing :)

I'll amend the sclo-python version of the macro files to explain that
more clearly, and probably put something in the pyscl-devel README as


Nick Coghlan
Red Hat Platform Engineering, Brisbane

More information about the SCLorg mailing list