j...@macports.org writes:
Revision: 116220
https://trac.macports.org/changeset/116220
Author: snc at macports.org
Date: 2014-01-21 13:14:00 -0800 (Tue, 21 Jan 2014)
Log Message:
---
py-turbogears, py-turbokid: remove python24, maintainer timeout #35623
Instead of
Those packages were blocking the removal of python24 subports that I maintain
(e.g py-elementtree).
100% agree with removing at least the python24 modules like Sean said. Also,
people are quite capable of pulling python24’s modules out of our repository
after removal if they need them.
While
I agree. I think all py24-* ports should be removed now. Removing py24-* ports
will change the default python to 2.7 for people who (mistakenly) install
py-foo. I would not object to everything less than py27-* leaving too but maybe
later.
Cheers!
Frank
On Jan 22, 2014, at 9:11 AM, Jeremy
The one thing I'd caution against is removing any py24* ports that have no
newer versions. I cannot think of any off the top of my head, but I guess
that would just be something to check for while removing the py24* ports,
i.e., making sure that they have a version available for a newer python
(was: [116220] trunk/dports/python)
On Wed, Jan 22, 2014 at 5:11 PM, Jeremy Lavergne wrote:
Realistically, most modules below python27 should get axed.
I don't have anything against removing python 2.4 (or 2.5 for that
matter), but there is one specific use case speaking against removing
s...@macports.org writes:
ebori...@ieee.org writes:
Haven't had a chance to look into this; have you updated mpich-devel
(betas / etc), as well?
Yep. The two files are almost the same now and could even be merged into
one portfile to de-duplicate logic. Same goes for openmpi{,-devel}.
