[scl.org] Question about generating RPMs that depend on SCLs (like python27)

Alan Robertson alanr at unix.sh
Tue Jul 15 17:14:13 UTC 2014

So, my tool does not conflict with anything that RH or anyone else 
provides -- so it doesn't need to be an SCL package.  It just *depends* 
on an SCL package.  My code is perfectly happy to issue the scl commands 
when it needs to (it knows when it needs to).  No one has to issue any 
scl commands to run my code.

Both of those links seem to be oriented towards creating an SCL 
package.  Did I miss something?


On 07/15/2014 10:03 AM, Petr Kovar wrote:
> Hi,
> On Tue, 15 Jul 2014 10:52:43 -0500
> Eugene Vilensky <evilensky at gmail.com> wrote:
>> On Mon, Jul 14, 2014 at 4:06 PM, Alan Robertson <alanr at unix.sh> wrote:
>>> I'm creating an RPM (and spec file) that needs Python 2.7 (the python27
>>> scl).  When I generate it for RHEL6/CentOS6, I the RPM I create has some
>>> automatically generated dependencies which python27 does not seem to
>>> fulfill...
>> ​Hi Alan,
>> I'm only beginning to look into doing this for myself, but this might be
>> how your spec might need to be modified to be SCL aware?:
>> https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/1/html/Software_Collections_Guide/sect-Converting_a_Conventional_Spec_File.html
> A newer version of the doc is here:
> https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/2/html/Software_Collections_Guide/sect-Converting_a_Conventional_Spec_File.html
> This link might also be of help:
> https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/2/html/Software_Collections_Guide/sect-Extending_the_python27_and_python33_Software_Collections.html
>> HTH,
> pk
> _______________________________________________
> SCLorg mailing list
> SCLorg at redhat.com
> https://www.redhat.com/mailman/listinfo/sclorg

     Alan Robertson <alanr at unix.sh> - @OSSAlanR

"Openness is the foundation and preservative of friendship...  Let me claim from you at all times your undisguised opinions." - William Wilberforce

More information about the SCLorg mailing list