1 |
If you're like me, then maybe you wondered, where is Python 2.1.1? |
2 |
|
3 |
Here is how to build your own Python 2.1.1 without using .ebuild. The |
4 |
patches mentioned here are attached. |
5 |
|
6 |
1. first fix tcl-tk .ebuild |
7 |
a) become root: su |
8 |
b) go to portage dir: cd /usr/portage |
9 |
c) apply my patch to tcl-tk-8.4.2.ebuild: patch -p0 < /path/to/tcl-tk.patch |
10 |
d) remerge tcl-tk: emerge dev-lang/tcl-tk |
11 |
e) become yourself: exit |
12 |
2. get Python-2.1.1.tgz |
13 |
3. untar it: tar zxf Python-2.1.1.tgz |
14 |
4. go to Python-2.1.1 directory: cd Python-2.1.1 |
15 |
5. make a little config-command file, just in case you need to rerun the |
16 |
./configure script: |
17 |
echo './configure --prefix=/usr/local/python2.1' > config-command |
18 |
6. run it: sh config-command |
19 |
7. go outside of Python-2.1.1 dir: cd .. |
20 |
8. apply my patch to Setup file: |
21 |
patch -p0 < /path/to/Python-Setup.patch |
22 |
9. go back: cd Python-2.1.1 |
23 |
10. run make: make |
24 |
11. become root: su |
25 |
12. install Python: make install |
26 |
13. become yourself: exit |
27 |
|
28 |
That should be all. If you don't want old db support, then add |
29 |
'--without-libdb' option to the ./configure command above. |
30 |
|
31 |
I was going to make an .ebuild for this, but I realized it would be waste of |
32 |
time, since I am not a gentoo developer, and it would take me a long time to |
33 |
learn how portage system works. I am happy just being a user. |
34 |
|
35 |
I hope this helps. |
36 |
|
37 |
--Leo |