On 2018-08-08 10:47, Jason Tibbitts wrote:
"JF" == John Florian <jflor...@doubledog.org> writes:
JF> How difficult would it be to provide modern Python (e.g. 35 or 36)
JF> in EPEL?
Obviously not that difficult, since it is already there.
By that I assume you mean 34, right? Or am I overlooking something?
The main
problem is that the way it was done requires that Fedora specfiles grow
additional complication in order to be built in EPEL, so it isn't just a
matter of rebuilding a bunch of existing packages.
IIRC, the Software Collection stuff has newer ones that I could use, but
all the install/setup stuff is cumbersome as compared to declaring a few
simple deps in my spec files. If you or anyone has references how to
pull SC deps in neatly, I'd love to see that.
I suppose I'm just in the same boat everyone else is where the life of
Fedora releases are too short to be ideal for production environments
and EL releases are just too old. Of course, if the Fedora releases
lived longer, they also would be(come) too old. It just seems EPEL
never quite lives up to what it ideally could be, the latest offerings
from Fedora atop EL.
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/message/FSYOZQJCO4325WAHLBO6UHT4VXU6PLD7/
