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