So, let's not do that again? Use a virtualenv whenever you need local packages of things that aren't in Portage. You can even direct link to the main script so you don't have to enter the virtualenv just to use it.
This, run as root, will show what packages are not handled by Portage. You can then examine the output and run `pip uninstall` (as root) on the package names.
Code: Select all
pip list | while read l a; do loc=$(pip show "$l" | fgrep Location | awk '{ print $2 }') && find "${loc}" '(' -name "${l}*" -o -name "${l//-/_}*" ')' | head -n 1 | xargs qfile >/dev/null || echo "$l"; done
(Explanation: Parse pip list, take first argument (called l), get the information, take the Location line, get the path, search for the path + package_name, pass the arguments to qfile. If qfile fails, echo the package name (it means it is not handled by Portage).)
If you get nothing for output, that means either an error occurred or Portage is managing all your files that would have come via Pip.