| 1 |
On Sat, 23 May 2009 03:51:40 -0700 (PDT) |
| 2 |
Jon Hardcastle <jd_hardcastle@×××××.com> wrote: |
| 3 |
|
| 4 |
> > |
| 5 |
> > And finally, couldn't he have gotten a binary package from |
| 6 |
> > http://tinderbox.dev.gentoo.org/default-linux/x86/dev-lang/ |
| 7 |
> > ? |
| 8 |
Have you not yet tried to get python from a binary package? |
| 9 |
See http://forums.gentoo.org/viewtopic-p-4669397.html#4669397 |
| 10 |
That is both the easiest and cleanest solution I have found so far, |
| 11 |
(not that I have researched much, I admit). |
| 12 |
And maybe you don't even have to extract the tarball manually with |
| 13 |
tar; maybe you can use qmerge from app-portage/portage-utils |
| 14 |
(AFAIK it is written in C). |
| 15 |
|
| 16 |
Now, I do have concerns about your system having remains of multiple |
| 17 |
python installations. |
| 18 |
|
| 19 |
Any person with python knowledge can give an opinion on whether this |
| 20 |
is dangerous? And what is the easiest way to clean the mess? |
| 21 |
|
| 22 |
One idea: you can can recompile python with a safe |
| 23 |
prefix (such as a subdir of your home), issue make install (not as root, |
| 24 |
for increased safety) and see where Python install its files relative to |
| 25 |
the prefix, so you can delete them from your system |
| 26 |
(to be more careful before deleting a file, you can issue |
| 27 |
qfile <FILE> to see if it is owned by a portage-installed package. |
| 28 |
And in the end you can emerge python properly, from the sources, so all |
| 29 |
the ebuild logic (which is more than just ./configure, make and make install) |
| 30 |
gets applied, and you get a Python installation that respects your USE flags, |
| 31 |
CFLAGS and other system-specific settings (obviously you don't get such a |
| 32 |
system-customized python when you use the binary package from tinderbox). |
Archives