On Thu, Jul 13, 2017 at 5:18 PM, Nick Coghlan <ncogh...@redhat.com> wrote: > On Wed, Jul 12, 2017 at 4:22 PM, Nick Coghlan <ncogh...@redhat.com> wrote: >> I wasn't planning to publish the COPR builds anywhere other than COPR, >> they'd just be a place for me to tinker with things before pushing >> them into CBS as real builds. > > I realised I'm going to want a public development repo to hold any > notes I make about the process, as well as any custom tools I build, > so I've created that here: https://github.com/ncoghlan/pyscl-devel/
Status update on this: - with some adjustments to the relevant spec files, I came up with an rpm-list-builder recipe that can bootstrap the whole rh-python35 SCL stack in a clean mock chroot in about an hour (depending on your system specs) - the README at https://github.com/ncoghlan/pyscl-devel/ covers how to run such a build yourself if you're so inclined As noted at https://github.com/ncoghlan/pyscl-devel/issues/1, the next steps will be to switch the built SCL name over to "sclo-python", and then get it building in COPR using actual bootstrap component releases rather than private RPM builds with tweaked release tags. I still have a PyCon Australia talk to finish, though, so I'm planning to take a break from working on this until after that's done. I'm definitely open to PRs if anyone wanted to take a look at what's involved in the rename in the meantime :) Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane _______________________________________________ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
