Apparently more people like this change. I'll get back to trac ticket and start working on this. On Thu, Feb 21, 2008 at 12:39 AM, js <ebgssth@gmail.com> wrote:
Thanks for thorough explanation. That makes sense. The reason why I started this discussion is that I want to make python24 to be python25-like port. What if I created patches for this, Would you accept that changes?
well, what else do you want to change? There already are py-bsddb, py- readline, .. which provide modules not build by default (by the python24 port).
I'd like to drop modules from python24 the same way python25 do currently. This would help writing Portfile for python2[45] easier.
If you _really_ don't bother which python you end up with (and it doesn't matter if that changes), then you can use the "python_select: port to do just that. It basically provides symlinks to the real executables which you can change by calling python_select(1). Attention: If your port makes note of the exact location of you python executable, this might create an implicit dependency (which will cause breakage if you uninstall the "wrong" python)
No, I don't want default python on MacPorts. Explicit python24 and python25 would be clearer. just wanted to say python-minimal + py25-* ports would be nice.
To be honest, I also want to change py- prefix ports to py24- but this plan is rejected recently...
Rejected? Most probably due to the amount of work on both the project and the users' side. I think this would be cool, but if someone tackles this: Do a single commit on _all_ renamed ports and ports that depend on those AND write a mail to macports-users@ AND put something on the FAQ how to handle potential breakage.
If I prepared patches for this, would you bother to review/accept them?