> 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.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to