On Tuesday 05 August 2008, Dale wrote: > Andrew Gaydenko wrote: > > Thanks! > > > > Be sure, I'll want to (manually) unmerge those packages I remember > > and understand what do they do :-) > > > > > > Andrew > > I usually do this, equery depends <package name>. If it shows > something depends on it, don't remove it. Some things you do not > want to remove without making sure it is safe, python, emerge itself, > gcc, glibc, baselayout and anything with 'make' or 'conf' in the > name. Example, automake would be one to keep.
Why don't you just let portage do what it's best at and figure all that crap out by itself? It's much MUCH better at it than you. equery depends is broken. It doesn't actually consider USE flags and reports on stuff that is in DEPEND in the ebuild, even if it's conditional. Just examine the output of --depclean, see it there's any packages that you feel you want to keep, add them to world with 'emerge -n' and let --depclean do it's job. It will also never remove anything in system, which includes your entire build chain, portage and python. -- Alan McKinnon alan dot mckinnon at gmail dot com
