| 1 |
On Sun, 31 Mar 2013 09:09:56 -0400, Walter Dnes wrote: |
| 2 |
|
| 3 |
> emerge -p --depclean |
| 4 |
> |
| 5 |
> generates dire warnings. |
| 6 |
|
| 7 |
I wouldn't call this dire |
| 8 |
|
| 9 |
* Always study the list of packages to be cleaned for any obvious |
| 10 |
* mistakes. Packages that are part of the world set will always |
| 11 |
* be kept. They can be manually added to this set with |
| 12 |
* `emerge --noreplace <atom>`. Packages that are listed in |
| 13 |
* package.provided (see portage(5)) will be removed by |
| 14 |
* depclean, even if they are part of the world set. |
| 15 |
|
| 16 |
There used to be big scary warnings in the past, but that was years ago |
| 17 |
and depclean seems very reliable now. I'd certainly trust a feature |
| 18 |
maintained by the portage devs more than a home-brewed script |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
Neil Bothwick |
| 23 |
|
| 24 |
There's a fine line between fishing and standing on the shore looking |
| 25 |
like an idiot. |
Archives