[scl.org] How to submit patches for SCLs

[Noah Kantrowitz]

Will patches there end up in RHSCL too or do I need to send all patches to some magical place in RedHat too?

--Noah

> On Jun 10, 2016, at 12:13 AM, Dominic Cleal <dominic at cleal.org> wrote:
> 
> On 10/06/16 01:44, Noah Kantrowitz wrote:
>> Specifically looking at SCL packages that are originally from RHSCL. I think that means I would need to send patches for the spec files to RedHat but I can't figure out where those specs actually live (i.e. which git repo to send a patch in for). Anyone have a direction to look at? Taking rh-python34 as an example, SCLo links to COPR (https://copr.fedorainfracloud.org/coprs/rhscl/rh-python34-el7) but COPR links to 404'd git repo (http://copr-dist-git.fedorainfracloud.org/cgit/rhscl/rh-python34-el7/rh-python34.git).
> 
> It might be that the Copr builds on softwarecollections.org were from
> before Copr added dist-git support.
> 
> Anyway, you'll find specs for all of the builds in the CentOS SCLo SIG
> under this GitHub org: https://github.com/sclorg-distgit, with one repo
> per component and branches within. I don't know if anybody's paying
> attention to pull requests, you might need to contact the maintainer too.
> 
> --
> Dominic Cleal
> dominic at cleal.org
> 
> _______________________________________________
> SCLorg mailing list
> SCLorg at redhat.com
> https://www.redhat.com/mailman/listinfo/sclorg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://listman.redhat.com/archives/sclorg/attachments/20160610/e4d9397a/attachment.sig>