<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 2, 2014 at 6:25 AM, Jim Perrin <span dir="ltr"><<a href="mailto:jperrin@centos.org" target="_blank">jperrin@centos.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><br>
<br>
On 09/02/2014 08:16 AM, Karanbir Singh wrote:<br>
> hi<br>
><br>
> now that EPEL has moved out of beta, what are the next steps needed to<br>
> get epel-release included in CentOS-Extras.<br>
><br>
> - KB<br>
><br>
<br>
<br>
</div>Re-signing the package with the centos key, and then adding it to the<br>
repo. I don't see a need to do anything else.<br><br></blockquote><div><br></div><div>I think it's also worth considering if you want %config or %config(noreplace) for the .repo file in the package. We touched on this briefly in the EPEL meeting and Ansii opened a bug to track it: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1135576">https://bugzilla.redhat.com/show_bug.cgi?id=1135576</a></div>
<div><br></div><div>FWIW, epel-release-6 is %config(noreplace) on the repo file -- meaning it won't overwrite user-modified repo files. It might be worthwhile to have %config for the initial release of epel-release-7 (specifically to ensure that "gpgcheck=1" gets added), but after that I'd rather see it as "noreplace". I'll comment on the bug to see if we can get that sorted out.</div>
<div><br></div><div>-Jeff</div></div><br></div></div>