It might be nice to provide an sclo-python35 and sclo-python36 so that users such as we have an easier time not updating. I hope we will not for a long time be in the situation between python 2.7 and python 3, but it could happen between 36 and 37 for any of a number of reasons. However, that implies more work to get it set up. It becomes non-automated as 37 comes out.
Thoughts? -----Original Message----- From: sclorg-boun...@redhat.com [mailto:sclorg-boun...@redhat.com] On Behalf Of Nick Coghlan Sent: Thursday, July 13, 2017 10:54 PM To: sclorg@redhat.com Subject: [scl.org] RPM list builder & RHSCL rebuild recipes In putting together the todo list for the sclo-python SCL, Red Hat's Python maintenance team pointed me towards some of the tools used to maintain the Red Hat SCLs: https://github.com/ncoghlan/pyscl-devel/issues/1#issuecomment-315037884 In particular, RPM List Builder automates running through a series of packages builds based on a YAML recipe file: https://github.com/sclorg/rpm-list-builder/blob/master/docs/users_guide.md That then allows the build sequence for an SCL (including any required bootstrapping builds) to be automated. For example, the Python 3.5 SCL build sequence: https://github.com/sclorg/rhscl-rebuild-recipes/blob/master/python.yml#L87 These aren't currently mentioned in the SCL guide or on the SCLo-SIG wiki, so I figured I'd start by posting a message about them here, and then after I have the sclo-python SCL up and running try to come up with some suitable documentation updates. Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane _______________________________________________ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg _______________________________________________ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
