Just as you said, it might not so easy to fix things all now, but I think changes for better are a good thing and worth the effort. Everyone love to see consistent system layout, right? And having a beautiful system forces the system to remain same, I think.
On Feb 4, 2008 1:10 AM, Ryan Schmidt <[EMAIL PROTECTED]> wrote: > On Feb 2, 2008, at 18:06, [EMAIL PROTECTED] wrote: > > > js> So IMHO using py24 prefix for 2.4 port would be more > > intuitive. > > > > js> What do you think of this? > > > > +1. In fact, with Python 2.6 and 3.0 on the way I suspect it would > > be best > > to add version numbers to all versions of Python for awhile. > > It has already been established that python 2.5 ports shall have the > py25 prefix and python 3.0 ports shall have the py30 prefix. If > there's a python 2.6 version coming, then these should use the py26 > prefix. Python 2.4 ports use the py prefix because we had not > established the rules at that time and it is a major hassle to change > this now. There are a handful of ports that depend on python 2.3, but > none of them are in the python category, so none of them have a py > prefix. There are ports for python 2.2 and python 2.1 but I don't see > any ports that depend on those. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-users
