<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 20 March 2014 12:02, Remi Collet <span dir="ltr"><<a href="mailto:Fedora@famillecollet.com" target="_blank">Fedora@famillecollet.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
RHSCL 1.0 is GA since September.<br>
<br>
RHSCL 1.1 Beta is released today:<br>
<a href="http://developerblog.redhat.com/2014/03/20/rhscl-1-1-beta-available-apache-mongodb/" target="_blank">http://developerblog.redhat.com/2014/03/20/rhscl-1-1-beta-available-apache-mongodb/</a><br>
<br>
As EPEL is the common repository to find additional packages for RHEL, I<br>
really think it should also be possible to provide additional packages<br>
for RHSCL.<br>
<br></blockquote><div><br></div><div>I have been thinking about this and wondering if SCL's might be better under Robyn's "EPIC" (Extra Packages for Infrastructure and Clouds) which would be something that could have less rigid rules for keeping going for 12 years that would be more in line with SCL's 2-3 year lifetimes. I was going to bring it up as a FLOCK talk to get the ball running with possible interaction with the CentOS group (maybe joining with their SCL operations). Does that make sense?</div>
<div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
For now the Fedora Guidelines are still under discussion.<br>
<br>
Most of the discussion is about the tree layout (/var, /etc/, ...).<br>
This Guidelines will probably need more work/time before approval :(<br>
<br>
Of course, if some "new" SCL (new, as not in upstream product) will come<br>
to EPEL, it will have to follow the same Guidelines.<br>
<br>
But, for additional packages for existing collections (I mean extending<br>
RHSCL), thinks can be simpler. We only have to use the tree as defined<br>
in the RHSCL collection (in the meta-package).<br>
<br>
I really hope we can find some solution.<br>
<br>
Of course, we need to ensure, with rel-eng, that we are able to build<br>
those packages.<br>
<br>
<br>
So, time to raise the discussion.<br>
<br>
<br>
Remi.<br>
<br>
<br>
P.S. you will notice that whatever we decide, things will happen (and<br>
have already start), we just need to know if we want to see this in EPEL<br>
or outside.<br>
_______________________________________________<br>
epel-devel mailing list<br>
<a href="mailto:epel-devel@lists.fedoraproject.org">epel-devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/epel-devel" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/epel-devel</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Stephen J Smoogen.<br><br></div>
</div></div>