On 04/19/13 21:34, Neil Bothwick wrote:
On Fri, 19 Apr 2013 14:27:25 -0600, Joseph wrote:
Can someone explain me why am I getting long list of packages when I
run: emerge --depclean
Please post the exact command you used and the complete output.
--
Neil Bothwick
Hors d'oeuvres: 3 sandwiches cut into 40 pieces.
I always use: emerge --depclean -p
double check everything and then run: emerge --depclean
The reason, I'm asking as sometimes I see normal output
----------
* Depclean may break link level dependencies. Thus, it is
* recommended to use a tool such as `revdep-rebuild` (from
* app-portage/gentoolkit) in order to detect such breakage.
*
* Always study the list of packages to be cleaned for any obvious
* mistakes. Packages that are part of the world set will always
* be kept. They can be manually added to this set with
* `emerge --noreplace <atom>`. Packages that are listed in
* package.provided (see portage(5)) will be removed by
* depclean, even if they are part of the world set.
*
* As a safety measure, depclean will not remove any packages
* unless *all* required dependencies have been resolved. As a
* consequence, it is often necessary to run `emerge --update
* --newuse --deep @world` prior to depclean.
No packages selected for removal by depclean
Packages installed: 926
Packages in world: 206
Packages in system: 42
Required packages: 926
Number to remove: 0
------------
and on other system I have a list of all my packages scrolling by as I listed earlier.
--
Joseph
