On 16/06/15 12:28, Karanbir Singh wrote: > On 15/06/15 02:29, Lokesh Mandvekar wrote: >> Should've sent this earlier, but better late than never. >> >> At the last virt SIG meeting we were looking at good places to keep packages >> like cockpit, which I'm not sure belongs in a particular SIG yet. > > I believe there is a cockpit build in the CentOS Atomic Host repos now, > so maybe Atomic SIG might be the best place to park this at for now. > > the other way of looking at this might be: who's the target user base, > and within that which SIG delivers the most relevant content. Put stuff > closest to them. > >> Also, it was mentioned that we could make SIG repos depend on each other, and >> IIUC, KB has an example (in theory atleast) demonstrating that. >> >> Over to you KB.. > > Atomic SIG pulls from the Virt SIG packages, but neither are in a > released state, so there is no hard dependency in place there as yet. expanding on this, once content is 'released' the corrosponding centos-release-<sig>-component.rpm can have a requires: for the dependancy repo via a requires: centos-release-<other sig>-component handling this at the rpm level makes it simplistic to manage with existing tooling as well. > > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc