1 |
On 12/07/17 10:05, William L. Thomson Jr. wrote: |
2 |
> I should have caught that sooner. -c does not remove a package, it just |
3 |
> removes its deps. |
4 |
> |
5 |
> -c == --depclean. |
6 |
|
7 |
--depclean is doing exactly what it is supposed to. If called with no |
8 |
arguments, it searches for any unneeded dependencies and removes them, |
9 |
however if called with a package as an argument, it will remove that |
10 |
package *if it is not a dependency of another package*. Reporting |
11 |
"nothing to remove" is precisely what it's supposed to do, and using |
12 |
--verbose will tell you what is depending on the package. |
13 |
|
14 |
To be clear, running '--depclean foo' does not remove dependencies of |
15 |
foo, it removes foo provided it is not a dependency. It can be seen as a |
16 |
dependency-aware (and thus, generally safe) --unmerge. |
17 |
|
18 |
Making --depclean _always_ give you more information should just be a |
19 |
case of adding --verbose to EMERGE_DEFAULT_OPTS. |
20 |
|
21 |
> It is not the same as -C, which is remove a package directly. |
22 |
> |
23 |
> --unmerge (-C) |
24 |
|
25 |
Correct, --unmerge will remove a package without considering |
26 |
dependencies (give or take a few special cases). It is usually (or, at |
27 |
least, should generally be) reserved for those taking a hammer to a |
28 |
problem or with a particular desire to recover a broken system. |
29 |
|
30 |
Again, it's doing exactly what it's supposed to - removing a package |
31 |
you've told it to remove (unless it's one of the few |
32 |
almost-always-critical packages). |
33 |
|
34 |
-- |
35 |
Sam Jorna (wraeth) |
36 |
GnuPG ID: D6180C26 |