<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jan 16, 2014 at 6:28 PM, Toshio Kuratomi <span dir="ltr"><<a href="mailto:a.badger@gmail.com" target="_blank">a.badger@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Thu, Jan 16, 2014 at 04:47:04PM -0800, Dave Peterson wrote:<br>
><br>
> Wouldn't this be a perfect use case for Software Collections?<br>
><br>
> <a href="http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/" target="_blank">http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/</a><br>
> Software_Collections_Guide/index.html<br>
><br>
</div>I was considering this earlier and I'm a bit conflicted about that. There's<br>
several problems with this. The most obvious is that SCLs are rather coarse<br>
grained and we want to solve this for both the coarse grained stuff like<br>
(python interpreter) and fine grained things (like upgrading a single<br>
library)<br>
<br>
The second problem is that we don't just want these things for users to use. We also<br>
want them for our own use. But SCLs are meant to be isolated from the<br>
system.so we've mostly decided that things in the system shouldn't use SCLs<br>
to work. So we still need to solve the problem of newer python interpreter<br>
and newer django framework for use with apps that EPEL ships.<span><font color="#888888"></font></span><br></blockquote></div><br></div><div class="gmail_extra">What about having a separate EPEL repo for SCLs and/or these newest version of things? Like you mentioned before, this takes more work, but if then those that want the stable base can have it and those that want the newest can have it as well.<br>
</div></div>