| 1 |
When I run: emerge --depclean |
| 2 |
entire portage tree scrolling by what is causing it? |
| 3 |
|
| 4 |
It should be something like this: |
| 5 |
emerge --depclean -p |
| 6 |
|
| 7 |
* Always study the list of packages to be cleaned for any obvious |
| 8 |
* mistakes. Packages that are part of the world set will always |
| 9 |
* be kept. They can be manually added to this set with |
| 10 |
* `emerge --noreplace <atom>`. Packages that are listed in |
| 11 |
* package.provided (see portage(5)) will be removed by |
| 12 |
* depclean, even if they are part of the world set. |
| 13 |
* |
| 14 |
* As a safety measure, depclean will not remove any packages |
| 15 |
* unless *all* required dependencies have been resolved. As a |
| 16 |
* consequence, it is often necessary to run `emerge --update |
| 17 |
* --newuse --deep @world` prior to depclean. |
| 18 |
|
| 19 |
Calculating dependencies... done! |
| 20 |
>>> No packages selected for removal by depclean |
| 21 |
>>> To see reverse dependencies, use --verbose |
| 22 |
Packages installed: 778 |
| 23 |
Packages in world: 173 |
| 24 |
Packages in system: 43 |
| 25 |
Required packages: 778 |
| 26 |
Number to remove: 0 |
| 27 |
|
| 28 |
-- |
| 29 |
Joseph |
Archives