= Python.framework transition =

See the [browser:branches/python-frameworks] branch.

== Build python{24,25,30} ports as frameworks ==
(into ${prefix}/Library/Frameworks/Python.framework/Versions/{2.4,2.5,3.0}/)

 * Move the files from the framework into the "usual" location and add the following symlinks:
{{{
${framewdir}/Python.framework/Versions/2.5/lib/python2.5 -> ${prefix}/lib/python2.5

${framewdir}/Python.framework/Versions/2.5/lib/libpython*.dylib -> ${prefix}/lib/libpython*.dylib

${framewdir}/Python.framework/Versions/2.5/include/python2.5 -> ${prefix}/include/python2.5

${framewdir}/Python.framework/Versions/2.5/bin/$foo -> ${prefix}/bin/$foo
}}}

  Also see the post-destroot in the proposed [browser:branches/python-frameworks/dports/lang/python25/Portfile new python25] port for details.

 * Make python_select aware of the new paths
   * Python.framework/{Headers,Resources,Python,Versions/Current}
   * libpython*.dylib

== Further transition work ==

=== python24 ===
python24 is already a framework installation, but should be changed to match
the scheme from above.

=== python25 ===
In order to safely upgrade especially python25 to a framework, we need:

    * No changes to the python port groups needed

=== python30 ===
Nobody should be using python30 productively yet. python30 port group was also
not released yet.
    * Make python30 install the same as other python versions.

=== python26 ===
After all was sorted out, we can add a python26 port in the same manner for the upcoming next python release.