From: Jorge Morais <please.no.spam.here@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ARGH I uninstalled python
Date: Wed, 27 May 2009 09:49:38 -0300 [thread overview]
Message-ID: <20090527094938.4b31aa9b@gmail.com> (raw)
In-Reply-To: <20090523190850.1c529701@gmail.com>
On Sat, 23 May 2009 19:08:50 -0300
Jorge Morais <please.no.spam.here@gmail.com> wrote:
> One idea: you can can recompile python with a safe
> prefix (such as a subdir of your home), issue make install (not as root,
> for increased safety) and see where Python install its files relative to
> the prefix, so you can delete them from your system
> (to be more careful before deleting a file, you can issue
> qfile <FILE> to see if it is owned by a portage-installed package.
> And in the end you can emerge python properly, from the sources, so all
> the ebuild logic (which is more than just ./configure, make and make install)
> gets applied, and you get a Python installation that respects your USE flags,
> CFLAGS and other system-specific settings (obviously you don't get such a
> system-customized python when you use the binary package from tinderbox).
>
I should mention that you should be careful about deleting any files -
and qfile is not a 100% guarantee that the file does not come from a
Portage-installed package. For example, in my system Python was
installed by Portage, and
$ file /usr/bin/python
/usr/bin/python: symbolic link to `python2.5'
, yet
$ qfile /usr/bin/python
<No output>
So qfile giving an empty output is not a guarantee that the file is
indeed orphan. Specially with symlinks - look at the Python ebuild
and see the way these symlinks are generated.
And of course, it is wise to emerge --buildpkg python before doing any
cleaning.
And after the cleaning, reemerge Python.
Regards,
Jorge
next prev parent reply other threads:[~2009-05-27 12:45 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 10:51 [gentoo-user] ARGH I uninstalled python Jon Hardcastle
2009-05-23 22:08 ` Jorge Morais
2009-05-24 8:52 ` Keith Dart
2009-05-24 10:09 ` Jorge Morais
2009-05-24 12:31 ` Keith Dart
2009-05-24 9:08 ` Alan McKinnon
2009-05-24 13:07 ` Jorge Morais
2009-05-27 12:49 ` Jorge Morais [this message]
2009-05-27 20:28 ` Wyatt Epp
2009-05-27 21:06 ` Jorge Morais
2009-05-27 21:55 ` Neil Bothwick
2009-05-28 9:37 ` Wyatt Epp
-- strict thread matches above, loose matches on Subject: below --
2009-05-27 8:32 Jon Hardcastle
2009-05-27 9:47 ` Neil Bothwick
2009-05-27 12:29 ` Jorge Morais
2009-05-27 12:55 ` Stroller
2009-05-23 10:50 Jon Hardcastle
2009-05-22 23:36 Jon Hardcastle
2009-05-23 0:03 ` Dale
2009-05-23 1:33 ` Arttu V.
2009-05-23 11:11 ` Dale
2009-05-23 11:52 ` Arttu V.
2009-05-23 11:59 ` Dale
2009-05-23 20:02 ` Neil Bothwick
2009-05-23 21:08 ` Dale
2009-05-24 9:07 ` Alan McKinnon
2009-05-24 9:28 ` Neil Bothwick
2009-05-24 10:06 ` Alan McKinnon
2009-05-24 12:17 ` Dale
2009-05-24 14:26 ` Neil Bothwick
2009-05-24 15:33 ` Dale
2009-05-24 16:22 ` Alan McKinnon
2009-05-24 17:26 ` Dale
2009-05-24 17:54 ` Alan McKinnon
2009-05-24 18:06 ` Arttu V.
2009-05-24 18:54 ` Alan McKinnon
2009-05-24 19:32 ` Volker Armin Hemmann
2009-05-24 20:51 ` Neil Bothwick
2009-05-24 22:56 ` Arttu V.
2009-05-24 18:11 ` Dale
2009-05-24 18:56 ` Alan McKinnon
2009-05-24 19:15 ` Dale
2009-05-24 20:41 ` Neil Bothwick
2009-05-24 21:09 ` Dale
2009-05-24 23:34 ` Stroller
2009-05-23 12:33 ` Alan McKinnon
2009-05-23 13:16 ` Dale
2009-05-23 7:55 ` Jorge Morais
2009-05-23 10:34 ` Jorge Morais
2009-05-22 23:05 Jon Hardcastle
2009-05-22 23:13 ` Michal Sroka
2009-05-22 23:19 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090527094938.4b31aa9b@gmail.com \
--to=please.no.spam.here@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox