1 |
On 04/20/13 07:32, Daniel Pielmeier wrote: |
2 |
>Joseph schrieb am 20.04.2013 03:09: |
3 |
>> On 04/19/13 21:34, Neil Bothwick wrote: |
4 |
>>> On Fri, 19 Apr 2013 14:27:25 -0600, Joseph wrote: |
5 |
>>> |
6 |
>>>> Can someone explain me why am I getting long list of packages when I |
7 |
>>>> run: emerge --depclean |
8 |
>>> |
9 |
>>> Please post the exact command you used and the complete output. |
10 |
>>> |
11 |
>> |
12 |
>> I always use: emerge --depclean -p |
13 |
>> double check everything and then run: emerge --depclean |
14 |
>> |
15 |
>> The reason, I'm asking as sometimes I see normal output |
16 |
><SNIP> |
17 |
>> |
18 |
>> |
19 |
>> and on other system I have a list of all my packages scrolling by as I |
20 |
>> listed earlier. |
21 |
> |
22 |
>Pretty much sure there is a "-v" somewhere. I mean "emerge --depclean |
23 |
>-p" vs. "emerge --depclean -pv". As with -v the output looks like the |
24 |
>one you described. |
25 |
> |
26 |
>-- |
27 |
>Regards |
28 |
>Daniel |
29 |
|
30 |
No I'm not putting any "-v" on the command line, I use "|more" as the catch the beginning: |
31 |
-------------- |
32 |
# emerge --depclean -p |more |
33 |
|
34 |
* Depclean may break link level dependencies. Thus, it is |
35 |
* recommended to use a tool such as `revdep-rebuild` (from |
36 |
* app-portage/gentoolkit) in order to detect such breakage. |
37 |
* |
38 |
* Always study the list of packages to be cleaned for any obvious |
39 |
* mistakes. Packages that are part of the world set will always |
40 |
* be kept. They can be manually added to this set with |
41 |
* `emerge --noreplace <atom>`. Packages that are listed in |
42 |
* package.provided (see portage(5)) will be removed by |
43 |
* depclean, even if they are part of the world set. |
44 |
* |
45 |
* As a safety measure, depclean will not remove any packages |
46 |
* unless *all* required dependencies have been resolved. As a |
47 |
* consequence, it is often necessary to run `emerge --update |
48 |
* --newuse --deep @world` prior to depclean. |
49 |
|
50 |
Calculating dependencies ... done! |
51 |
app-admin/apache-tools-2.2.24 pulled in by: |
52 |
www-servers/apache-2.2.24 requires ~app-admin/apache-tools-2.2.24 |
53 |
|
54 |
app-admin/eselect-1.3.4 pulled in by: |
55 |
app-admin/eselect-fontconfig-1.1 requires >=app-admin/eselect-1.2.3 |
56 |
app-admin/eselect-lib-bin-symlink-0.1.1 requires app-admin/eselect |
57 |
app-admin/eselect-mesa-0.0.10 requires >=app-admin/eselect-1.2.4 |
58 |
app-admin/eselect-opencl-1.1.0-r1 requires >=app-admin/eselect-1.2.4 |
59 |
app-admin/eselect-opengl-1.2.6.1 requires >=app-admin/eselect-1.2.4 |
60 |
app-admin/eselect-php-0.6.2 requires >=app-admin/eselect-1.2.4 |
61 |
app-admin/eselect-pinentry-0.3 requires app-admin/eselect |
62 |
app-admin/eselect-postgresql-1.0.10 requires app-admin/eselect |
63 |
app-admin/eselect-python-20111108 requires >=app-admin/eselect-1.2.3 |
64 |
app-admin/eselect-qtgraphicssystem-1.1.1 requires >=app-admin/eselect-1.2.4 |
65 |
app-admin/eselect-ruby-20100603 requires >=app-admin/eselect-1.0.2 |
66 |
app-admin/eselect-wxwidgets-1.4 requires >=app-admin/eselect-1.2.3 |
67 |
app-admin/eselect-xvmc-0.3 requires >=app-admin/eselect-1.0.10 |
68 |
sys-apps/portage-2.1.11.55 requires >=app-admin/eselect-1.2 |
69 |
|
70 |
app-admin/eselect-fontconfig-1.1 pulled in by: |
71 |
------------- |
72 |
|
73 |
So I don't understand why it is listing all my packages. |
74 |
|
75 |
-- |
76 |
Joseph |