1 | | = Python.framework transition = |
2 | | |
3 | | See the [browser:branches/python-frameworks] branch. |
4 | | |
5 | | == Build python{24,25,30} ports as frameworks == |
6 | | (into ${prefix}/Library/Frameworks/Python.framework/Versions/{2.4,2.5,3.0}/) |
7 | | |
8 | | * Move the files from the framework into the "usual" location and add the following symlinks: |
9 | | {{{ |
10 | | ${framewdir}/Python.framework/Versions/2.5/lib/python2.5 -> ${prefix}/lib/python2.5 |
11 | | |
12 | | ${framewdir}/Python.framework/Versions/2.5/lib/libpython*.dylib -> ${prefix}/lib/libpython*.dylib |
13 | | |
14 | | ${framewdir}/Python.framework/Versions/2.5/include/python2.5 -> ${prefix}/include/python2.5 |
15 | | |
16 | | ${framewdir}/Python.framework/Versions/2.5/bin/$foo -> ${prefix}/bin/$foo |
17 | | }}} |
18 | | |
19 | | Also see the post-destroot in the proposed [browser:branches/python-frameworks/dports/lang/python25/Portfile new python25] port for details. |
20 | | |
21 | | * Make python_select aware of the new paths |
22 | | * Python.framework/{Headers,Resources,Python,Versions/Current} |
23 | | * libpython*.dylib |
24 | | |
25 | | == Further transition work == |
26 | | |
27 | | === python24 === |
28 | | python24 is already a framework installation, but should be changed to match |
29 | | the scheme from above. |
30 | | |
31 | | === python25 === |
32 | | In order to safely upgrade especially python25 to a framework, we need: |
33 | | |
34 | | * No changes to the python port groups needed |
35 | | |
36 | | === python30 === |
37 | | Nobody should be using python30 productively yet. python30 port group was also |
38 | | not released yet. |
39 | | * Make python30 install the same as other python versions. |
40 | | |
41 | | === python26 === |
42 | | After all was sorted out, we can add a python26 port in the same manner for the upcoming next python release. |