F21 System Wide Change: SCL

[Marcela Mašláňová]

On 04/16/2014 07:36 PM, Dennis Gilmore wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, 14 Apr 2014 14:13:24 +0200
> Jaroslav Reznik <jreznik at redhat.com> wrote:
>
>> = Proposed System Wide Change: SCL =
>> https://fedoraproject.org/wiki/Changes/SCL
>>
>> Change owner(s): Marcela Mašláňová <mmaslano at redhat.com>
>>
>> SCL - Software Collections - are popular packaging format above rpm.
>> Let's enable them for Fedora. More details on upstream page [1].
>>
>> == Detailed Description ==
>> My first draft [2] is obsoleted by current state of SCL, Copr... I
>> would keep the SCL workflow simple as possible.
>>
>> Playground repo
>>
>> 1. Build SCL in Copr
>> 2. Add SCL into Playground repo
>>
>> Fedora main repo
>>
>> 0. Build SCL in Copr (or use existing SCL)
>> 1. Do standard package review
>> 2. Upload packages into git - specific branch based on Fedora version
>> and name of collection. For stable repo we must be able to replicate
>> builds from git repo, which Fedora own.
>> 3. Build SCL in koji or magically add SCL builds from Copr (depends
>> on preference of releng)
>>
>> SCL living on Copr can be good candidates for inclusion in Fedora.
>> Maintainer of such SCL must be able create Change proposal for his
>> collection. Review of packages in the collection should depend on
>> repository (Playground - almost no rules, Fedora - standard
>> guidelines).
>>
>> == Scope ==
>> * Proposal owners:
>> 0. Approve SCL guidelines by FPC
>> 1. Include one collection into Fedora Playground repository or into
>> main Fedora repository (probably the one wanted by Cloud WG). It
>> might be this one rebuild for Fedora [3]. Updates of some gems or
>> addition of other gems might be needed. Review by Cloud projects is
>> needed.
>>
>> * Other developers: If SCL is in Fedora, maybe some other project can
>> use it for their work.
>>
>> * Release engineering: Magically add SCLs builds into compose or set
>> up koji for SCLs.
>
> building in koji is a must
>
> Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQIcBAEBAgAGBQJTTr+GAAoJEH7ltONmPFDRhmgQAM/wINQyNmOjyBzgTHCNAe3D
> pfndiCl7O39EQPTs6vV9PpPGN5TXUhgStwtRTTMuRegevgFchhjxWXknjp9RQSEo
> StrHxkJZ5+pEcFaR+2hTqIKSg10O3hYYT+p9kZjMKEfJ3+NUqvJNv9hmcBdeTI0F
> /hDDqezQsE+Gk8xWMVv0GeCN1+HPM9GWotO4YpnITgCU+IMleM5Nxjr1mJzab8nA
> /vS+Zh9VnV6wpxuegqcmR8qSufDEsptyU3ZxqddqP+ZNehtag4GnMCwX7w30XQH7
> FlhIeTYrDFrbMowVnEtur6Udwi2PHe4vBe6jZILclCyJ3si7hXrCEsaRP/a7a9OX
> bkownl9Lvo/v+w19SKDYm0c/Ojn1U8Ej4RN9pjVmpgJLFC/XARWI7Eov57MFPkZF
> k3IYppkAUreaXBxsLcnKdx3EJNBKTqjqJL3dFBCJJmn0Py1M2K9Q5Pp9Rr+BrtSW
> Faac9g4xh+fk1zIV8j5ItcQGrZg5ZJvmkXGeZjksQyIS99HrazYMG5cWe6n58jbM
> bikvItU9NKNpuxUK0/sBDhxsBn0XjYdXPl32A29QxIC6oX6sSaEAOrzEDOGW1M5n
> 8F7+zcTT0gF4gJh3e3/Hr2tR4pv3+hiKWVPutQLWYbIO/JWthdnWIc+QQ6WRegit
> LxRI4dsdJg5wrJS1JmPu
> =Mw6h
> -----END PGP SIGNATURE-----
>
Great, we can discuss how to do it. Usually it's needed to add into 
buildroot the meta-package for the collection. I guess what's needed 
from release engineering point of view can be explained by your 
colleagues from release engineering like Lubos.

Marcela