<div dir="ltr">If we're going to have a hackish approach regardless, is this something we could shoehorn into the image build process? I don't know much about the CentOS build infrastructure, but in Fedora we could do something like:<div>
<br></div><div>* Have the patch provided and an updated specfile in the git repo with the kickstart and other image metadata;</div><div>* At the start of the build, fetch the upstream libselinux sources and build an SRPM;</div>
<div>* Send that SRPM to koji to be built into a real RPM;</div><div>* Fetch the resulting RPM and install it into the image, either with the kickstart or with the Dockerfile we ship to stackbrew.</div><div><br></div><div>
We could probably even use Koji for EPEL-6 to do this, depending on how flexible the CentOS build infrastructure is. It's terrible and hackish and I hate it, but if it'll get us through until CentOS 6.6 (and will require less effort than other approaches), I say let's do it.</div>
<div><br></div><div>Or, could we use COPR to create a repo for the updated package? Again, stepping outside the CentOS infrastructure proper, but we're all owned by the same corporate overlord^W^W^W^W^W^W friends here.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 23, 2014 at 10:55 AM, Karanbir Singh <span dir="ltr"><<a href="mailto:mail-lists@karan.org" target="_blank">mail-lists@karan.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 05/21/2014 08:55 PM, Daniel J Walsh wrote:<br>
>> What are the opinions of the cloud-sig folks?<br>
> Yes that is what I would recommend, and is actually what we are doing<br>
> with RHEL6. New libselinux will show up in RHEL6.6 update but for now<br>
> only exists in rhel6.5 docker base image.<br>
<br>
</div>The way we are setup right now, we dont have any mechanism to push into<br>
specific repos, not a part of the OS repos, without some hoops - and the<br>
instance/image builders : that output the docker image, also only<br>
include the OS repos.<br>
<br>
Let me look the process over and see how we can do something like this,<br>
and how we might be able to repose these repos ( and where ).<br>
<br>
Regards<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Karanbir Singh<br>
<a href="tel:%2B44-207-0999389" value="+442070999389">+44-207-0999389</a> | <a href="http://www.karan.org/" target="_blank">http://www.karan.org/</a> | <a href="http://twitter.com/kbsingh" target="_blank">twitter.com/kbsingh</a><br>
GnuPG Key : <a href="http://www.karan.org/publickey.asc" target="_blank">http://www.karan.org/publickey.asc</a><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Chris St. Pierre
</div>