On Wed, Jul 12, 2017 at 4:22 PM, Nick Coghlan <ncogh...@redhat.com> wrote: > On Tue, Jul 11, 2017 at 11:39 PM, Honza Horak <hho...@redhat.com> wrote: >> This guide is actually not complete, as I've just realized -- copr is only >> one way to build SCLs for www.softwarecollections.org, but we can include >> SCLs from CBS (cbs.centos.org, build by SCLo SIG) as well. We should fix >> this part of documentation, thanks for pointing to it.. > > 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/ The identified steps for creating and publishing an initial version of sclo-python have been turned into an issue here: https://github.com/ncoghlan/pyscl-devel/issues/1 Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane _______________________________________________ SCLorg mailing list SCLorg@redhat.com https://www.redhat.com/mailman/listinfo/sclorg
