<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/25/2014 03:41 PM, Johnny Hughes
wrote:<br>
</div>
<blockquote cite="mid:535A57F4.10909@centos.org" type="cite">
<pre wrap="">On 04/24/2014 03:53 PM, Les Mikesell wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Thu, Apr 24, 2014 at 3:50 PM, Karanbir Singh <a class="moz-txt-link-rfc2396E" href="mailto:mail-lists@karan.org"><mail-lists@karan.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">rest of it is just hand waving
</pre>
</blockquote>
<pre wrap="">If you enjoy surprises.
</pre>
</blockquote>
<pre wrap="">
Well ... my opinion is this:
Just because the release RPM is in extras does not mean that people have
to (or will) install it. People have to "yum install epel-release"
before they get access to the repo.
I would assume if someone wanted to install the epel-release package,
the majority of them would want at least the main binary repository to
be enabled by default.
If someone wants EPEL installed and wants it instead off (I think by far
the minority ... does someone disagree?), they can modify their .repo
file manually to turn it off.
That being the case, I would think the best thing is that we just build,
sign, and push the current release file from the EPEL repo for c5 and c6
in our CentOS Extras .. in the appropriate spot.
Thoughts?
</pre>
</blockquote>
I have to play devil's advocate here. Quote from
<a class="moz-txt-link-freetext" href="http://lists.centos.org/pipermail/centos-devel/2014-February/009830.html">http://lists.centos.org/pipermail/centos-devel/2014-February/009830.html</a>:<br>
<blockquote>
<pre>there are more than 100 repos out there, which ones are we going to add and why and
then at that point what do the others need to do in order to also get
included ?
</pre>
</blockquote>
<br>
</body>
</html>