On Mon, Dec 1, 2014 at 9:36 AM, Brian Stinson <bstinson at ksu.edu> wrote: > Hi All, > > I would like to start a discussion on where/how to ship the package > building toolchain. Most of these tools shipped in EPEL, but deploying > them to one of our repos would allow us to maintain our own patches if > necessary and would eliminate any dependencies on 3rd party repositories > for our core tools. > I'd much rather not do this for a couple reasons: 1. CentOS Extras shouldn't overlap with EPEL. 2. If there are reasons to customize/patch some of these things for the CentOS infrastructure, perhaps they belong in a new/separate repo -- especially considering centos-extras is enabled by default. > > 1.) Some of the tools (koji especially) will require config > customization, what is the best way to handle that? > Isn't there some configuration management system in place? Or maybe I'm misunderstanding the question...? > > 2.) What should the testing -> release process look like after a koji > build is done? > Are you planning to have a testing/staging Koji instance running for people to QA? -Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20141201/7a4fffe4/attachment-0008.html>