> Jeremy, what Joshua is dancing around with his questions is that python 2.6
> and later use a drastically different layout (a framework layout) from python
> 2.5 and earlier. With python 2.6 and later, ports install their binaries in
> directories deep in the tree, and the portgroup provides the convenience of
> creating symlinks for them in ${prefix}/bin. With python 2.5 and earlier, the
> binaries are already installed in ${prefix}/bin to begin with.So if I've read this correctly * python24/python25 installs binaries without a suffix into the binary folder (which can collide?) * while anything newer (26, 27, 31, 32) buries them into versioned frameworks Depending on the python version the user is given (dependencies) files get named differently, not to mention you might end up with a failed install when py[24]-X collides with py25-X. And if the user still has an old python installed (since there are MacPorts installs that old) I don't see why having piecemeal results is ideal. Throw the inconsistencies away, as jwa was saying, because they are inconsistent and EOL.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
