On 28 January 2015 at 21:48, Tetsuya Morimoto <tetsuya.morimoto(a)gmail.com>
On Thu, Jan 29, 2015 at 5:05 AM, Stephen John Smoogen <smooge(a)gmail.com>
> On 27 January 2015 at 20:45, Tetsuya Morimoto <tetsuya.morimoto(a)gmail.com
> > wrote:
>> On Wed, Jan 28, 2015 at 12:24 PM, Orion Poplawski <orion(a)cora.nwra.com>
>>> On 01/27/2015 08:21 PM, Tetsuya Morimoto wrote:
>>>> For EPEL5, we can install python26 packages from epel repository.
>>> If I read the messages correctly, I believe this will be going away
>> Really? That's unfortunate.
>>>> It would be nice if we can install python3 (python33 or python34) as
>>>> same as python26.
>>> I'm sure it would be, but EL5 is OLD at this point and not getting much
>>> love in the volunteer space.
>> Yes, but RHEL5/CentOS5 support continues until 2017-03-31 (extended
>> support is 2020-03-31), so I just thought it would be nice. I'll contribute
>> some work if SCL repository is available on CentOS 5.x.
> It gets support because people are paying Red Hat to do various support
> work. Volunteer projects like EPEL, rpmforge, elrepo, SCL's etc rely on
> contributions of people willing to do the work. When people only take and
> no longer contribute, it begins to fall apart. [This comment is not aimed
> at you, it is more of a general comment that many consumers of these repos
> don't consciously understand.]
I see. I mean many consumers might use CentOS5 with python24 (or 26) until
2017-03-31. I think that providing python3 on CentOS5 makes them easy to
migrate a newer CentOS version (or Python 3), like ensurepip backported to
I agree. I would like to be able to provide a python27 and python3x in
EPEL-5. However the work required to do so is not small and my free time to
get it together and working is fleeting. If others have the time to do so,
I would greatly appreciate it.
epel-devel mailing list