Boyd Waters wrote: > I think that this is why I haven't committed anything; I've been > building all Python 2.5 stuff via MacPorts as a framework build for > about a year now. > > I had to modify all of my Python ports that I use so that they > understand the symlink.
Should be working out-of-the-box, once the python25 port group gets updated to install directly into the framework. > I attempted to modify MacPorts Tcl so that it would not die as it > attempted to traverse a symlink, but I failed. I must not understand > Tcl very well. It is not a problem of traversing the symlink, but the file_map.db stores the information that a symlink owned by pyhon25 is at this place. If a py25-* port tries to make a directory at this place, it will fail. > I am pretty sure I don't understand all the issues, I still think that > MacPorts versioning (-24, -25, -30) is profoundly flawed, aside from > installation issues. Do you have any other solution? This is a bit unrelated to the framework transition. Multiple versions of the same software also apply to gcc and perl. Rainer _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev