Python framework transition

[Boyd Waters]

> 	• because we change lib/python2.5 from a directory into a symlink.  
> Otherwise you will see errors with file_map.db.
> 	• Because of the directory-to-symlink change, deactivate/activate  
> does not work. This will be the main challenge.
>


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.

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.

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.

But I'd be happy to show my awful hacked-up Python ports...


   - boyd


Boyd Waters
Scientific Programmer
National Radio Astronomy Observatory
Socorro, New Mexico



On Mar 6, 2008, at 11:00 AM, Rainer Müller wrote:

> Hi Thomas,
>
> Following the IRC discussion from today with afb and mdickens, I wrote
> together a wiki page which documents how we want to do the  
> transition to
> build pythonXX as frameworks.
>
> http://trac.macosforge.org/projects/macports/wiki/PythonFrameworkTransition
>
> Any comments so far?
>
> Also see the new branch at branches/python-frameworks. I already
> committed the efforts from #11267 there. With the branch, we can  
> easily
> test the transition code.
>
> Rainer
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev