1 |
On Oct 21, 2013 6:59 PM, "Joseph" <syscon780@×××××.com> wrote: |
2 |
> |
3 |
> When I run: emerge --depclean entire portage tree scrolling by what is |
4 |
causing it? |
5 |
> |
6 |
> It should be something like this: |
7 |
> emerge --depclean -p |
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 |
> * * As a safety measure, depclean will not remove any packages |
16 |
> * unless *all* required dependencies have been resolved. As a |
17 |
> * consequence, it is often necessary to run `emerge --update |
18 |
> * --newuse --deep @world` prior to depclean. |
19 |
> |
20 |
> Calculating dependencies... done! |
21 |
>>>> |
22 |
>>>> No packages selected for removal by depclean |
23 |
>>>> To see reverse dependencies, use --verbose |
24 |
> |
25 |
> Packages installed: 778 |
26 |
> Packages in world: 173 |
27 |
> Packages in system: 43 |
28 |
> Required packages: 778 |
29 |
> Number to remove: 0 |
30 |
> |
31 |
> -- |
32 |
> Joseph |
33 |
> |
34 |
|
35 |
Have you set --verbose (-v) in make.conf as emerge default opts? |