[scl.org] rh-python36-build alternative in rhel

Jiri Novak jiri.novak at ghorland.net
Wed Nov 29 09:16:17 UTC 2017

Stefan Ring wrote:
> On Tue, Nov 28, 2017 at 2:40 PM, Jiri Novak <jiri.novak at ghorland.net> wrote:
>> Hi
>> I need to add more libraries to rh-python36, which would require using
>> rh-python36-build package and I've been told it is wring and I should do
>> my own SCL.
>> then I need to make the application use the extended SCL with added
>> libraries.
>> Just running it agains rh-python36 is not enough because of missing
>> dependencies :(
>> The specfile should create packages test-python36-build and
>> test-python36-runtime as a collection that extends rh-python36
> Is this even possible? If your collection is called test-python36, it
> will live in another directory hierarchy than rh-python36 and will not
> be able to access the packages from there. I think you're in for a
> world of pain.
> You can of course start a new collection by renaming everything in the
> rh-python36 package sources, picking up just the packages you need,
> thus creating a new, derived collection.

from what I know until now, it should be, but I might be wrong.
What else is the right way to make RPM adding more libraries available
when in scl enable rh-python36 bash?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 866 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/sclorg/attachments/20171129/1d6fe5d7/attachment.sig>

More information about the SCLorg mailing list