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

Davis, Daniel (NIH/NLM) [C] daniel.davis at nih.gov
Tue Sep 19 14:39:11 UTC 2017


Now that your question has been answered, let me ask mine.    The instructions to build pyscl-devel separate from Copr are not clear enough for me.   Are you suggesting that I run pipsi in a virtual environment?    How is scrlo-python involved?

I'm going to try later today, and want to be clear about what is involved...    I've built multi-package rpms before, sometimes from scripts and makefiles, but not multi-package repositories from scripts, and I've never used Copr and friends.   I've never used a chroot to build rpms, but I think I've installed mock even though I didn't really need it.

-----Original Message-----
From: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] On Behalf Of Nick Coghlan
Sent: Tuesday, September 19, 2017 4:10 AM
To: Petr Kubat <pkubat at redhat.com>
Cc: sclorg at redhat.com
Subject: Re: [scl.org] Setting SCL RPM build options in COPR?

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-pytho
>> n35-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-r
>> h/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-python
> 35-rh/rh-python35.spec#L113
> [2]
> https://github.com/sclorg-distgit/rh-python35/blob/sig-sclo7-rh-python
> 35-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 well.


Nick Coghlan
Red Hat Platform Engineering, Brisbane

SCLorg mailing list
SCLorg at redhat.com

More information about the SCLorg mailing list