-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22/09/15 16:52, Remi Collet wrote: > Le 21/09/2015 16:12, Haïkel a écrit : >> Hi, >> >> Since the CentOS acquihire, there was a lot of discussion about >> EPEL's future. Since the FOSDEM meetup between Fedora/CentOS >> folks, there was little progress on that topic > > Just enable EPEL in CBS, and that's all. > > Remi. > > > P.S. and explain to SIG member how to contribute to EPEL. > _______________________________________________ Well, adding so EPEL directly into cbs would then mean that all packages/repositories from cbs would have a hard require on epel too .. not something that target users would probably want (for packages conflicting/updating epel packages) What I'd be in favor of (short-term) would be more or less something like this : a cbs-epel target and rebuild (and keep in sync) epel packages in that target. Then, SIGs users/maintainers can just "tag" the builds already there (and that they'd like to see landing in their SIG repo) : mash will then generate correct repositories with repo closure without a hard dep on epel itself. That's just a "wild" idea (after a Rochefort beer ...), but I'd like to think a little bit more about that (and after having discussed with some people about the technical aspects) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYBp4UACgkQnVkHo1a+xU79wgCfSLocJss2f/Lq1PSS7SxJhyLh OF4AoJqjI80G0R/18Fy2iNK/Jh6P+ZuS =db5l -----END PGP SIGNATURE-----