| 1 |
The attached script takes the output of "emerge --pretend --depclean" |
| 2 |
and formats it into a script "cleanscript" which contains a set of |
| 3 |
"emerge --depclean" commands to remove individual items. Do *NOT* |
| 4 |
remove the "exit" and source "cleanscript". It's there to protect you. |
| 5 |
|
| 6 |
The script is very simple-minded about kernel-sources. I.e. it |
| 7 |
removes all but the latest version. E.g. I have 3 kernels in /usr/src, |
| 8 |
namely 2.6.31-r10, 2.6.32-r7, and 2.6.34-r1. I'm currently on |
| 9 |
2.3.32-r7. The script will want to remove 2.6.31-r10 and 2.6.32-r7 and |
| 10 |
keep 2.6.34-r1. I suspect that something similar may be true if you |
| 11 |
have multiple versions of gcc. Sources and gcc are a bit weird in that |
| 12 |
they're not "dependancies" of any packages, and they aren't listed in |
| 13 |
"world". |
| 14 |
|
| 15 |
One other thing I have noticed is that the format... |
| 16 |
"emerge --depclean =sys-boom/bah-1.2.3.4" |
| 17 |
...will not work if it's masked. autodepclean will find it, but you |
| 18 |
need to use "emerge --unmerge" to remove it. |
| 19 |
|
| 20 |
Other than that, the output from autodepclean seems to be OK. I've |
| 21 |
manually removed a bunch of stuff (cutting-&-pasting lines from |
| 22 |
cleanscript), and revdep-rebuild hasn't found any breakages. If you are |
| 23 |
unsure about any of its suggestions, please ask on this list. |
| 24 |
|
| 25 |
-- |
| 26 |
Walter Dnes <waltdnes@××××××××.org> |
Archives