| 1 |
> Thank you! Thank you! Thank you! |
| 2 |
> |
| 3 |
> I followed this |
| 4 |
> |
| 5 |
> http://blogs.pwmn.net/korkakak/2008/06/04/gentoo-i-unmerged-python-now-what |
| 6 |
> |
| 7 |
> which worked - in the end. couple of caveats tho for anyone 'that follows' get python from their site as the ftp link in this article is out of date. |
| 8 |
> |
| 9 |
> http://www.python.org/download/releases/ |
| 10 |
> |
| 11 |
> also I initially tried 3.01 and that didn't work so i installed 2.6.2 which worked 'out of the box' i then tested with 'emerge' and am now running 'emerge -va python' |
| 12 |
> |
| 13 |
> Cheers guys! |
| 14 |
> |
| 15 |
> Thanks to Dale too! |
| 16 |
|
| 17 |
Glad it worked. |
| 18 |
But, I don't know what will happen when the properly emerged python |
| 19 |
overwrites the manually installed Python. |
| 20 |
|
| 21 |
Does anybody know if the manual python install is "slotted", in the sense |
| 22 |
that it installs files in /usr/lib/python2.6, /usr/include/python2.6, etc? |
| 23 |
If it isn't, and Portage installs a slotted Python, the old files wouldn't |
| 24 |
be overwritten. |
| 25 |
And even if it is, the differences between the differently-configured and |
| 26 |
super-patched new python and the vanilla old python could result in |
| 27 |
a different set of file names, so it is possible that the old python |
| 28 |
will not be totally overwritten by the portage-emerged python. |
| 29 |
|
| 30 |
If I were you, I would at the very least read the log (specially its tail) |
| 31 |
of the python emerge (emerge logs normally go to /var/log/emerge). |
| 32 |
And you did log the files installed by the manual python install, |
| 33 |
didn't you? |
| 34 |
|
| 35 |
And why did you try python 3.01 first? You should try a similar vesion to |
| 36 |
what you were previously running. And specifically python 3.01 is crazy, |
| 37 |
as it is widely known that it is *not* compatible with python 2.x software. |
| 38 |
And did you properly uninstall python 3.0.1? |
| 39 |
|
| 40 |
Also, I didn't like the instructions in this blog very much. |
| 41 |
Wouldn't it be more appropriate to configure python like |
| 42 |
portage would? |
| 43 |
For example, in my system, where the last python install was |
| 44 |
dev-lang/python-2.5.4-r2 USE="ncurses readline ssl threads xml -berkdb -build -doc -examples -gdbm -ipv6 -sqlite -tk -ucs2 -wininst" |
| 45 |
|
| 46 |
the configure line was (from the log) |
| 47 |
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-fpectl --enable-shared --disable-ipv6 --infodir=${prefix}/share/info --mandir=${prefix}/share/man --with-libc= --enable-unicode=ucs4 --with-threads --build=i686-pc-linux-gnu |
| 48 |
|
| 49 |
Maybe it would be nice to install python to /usr/local (I'm not sure), |
| 50 |
but if you are going to install it in /usr (like portage), I think you |
| 51 |
might as well use the same configure line portage would. |
| 52 |
And if you wanted to be really clean, you could apply the patches that |
| 53 |
portage applies. |
| 54 |
|
| 55 |
And most importantly, |
| 56 |
*was this necessary*? |
| 57 |
Couldn't he have emerged python by invoking |
| 58 |
ebuild /usr/port/usr/portage/dev-lang/python/python-2.6.2.ebuild merge |
| 59 |
? |
| 60 |
This would do everyting correctly. |
| 61 |
And wouldn't it work without Python, since it is written in Bash? |
| 62 |
AFAIK, what needs Python is the high level interface to the portage |
| 63 |
system, while the low-level interface only needs Bash (but I'm |
| 64 |
totally not sure). |
| 65 |
|
| 66 |
And finally, couldn't he have gotten a binary package from |
| 67 |
http://tinderbox.dev.gentoo.org/default-linux/x86/dev-lang/ |
| 68 |
? |
Archives