On Mar 19, 2012, at 13:59, Jeremy Lavergne wrote: >> I think what Joshua is trying to say is that adding symlink support to 2.5 >> and earlier doesn't make sense. If you believe it does, could you provide a >> concrete example of a port, the files it installs, and the symlink you would >> like the portgroup to create (located where, pointing to where)? >> >> >> But recall this thread was supposed to be about removing python 2.4 (and >> 2.5), not spending further time on them. :) > > That's basically where I wanted to steer my argument before we had the dance > of questions. > > 1. Python-related behavior is fragmented, with different outcomes based on > the version--this should not be acceptable. As you noted, the work to make it > fall in line is more than we'd like to spend. > 2. The misfit Pythons are EOL. Let's drop them if not just for that reason, > to provide uniform experience to users.
I think we're agreed. But before we can remove python24 and python25 we need to do the project I mentioned yesterday, and find out what ports rely on them, and update them. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
