1 |
On Wed, 12 Jul 2017 14:17:30 +1000 |
2 |
"Sam Jorna (wraeth)" <wraeth@g.o> wrote: |
3 |
> |
4 |
> --depclean is doing exactly what it is supposed to. If called with no |
5 |
|
6 |
Problem is I was talking about removing packages directly. It served no |
7 |
purpose in this discussion. |
8 |
|
9 |
Since I use --depclean, not -c. I was assuming -c was unmerge like -C, |
10 |
but it is not. Others brought that up and sidetracked things. I just |
11 |
did not catch and mistakenly went down that wormhole. |
12 |
|
13 |
> |
14 |
> > It is not the same as -C, which is remove a package directly. |
15 |
> > |
16 |
> > --unmerge (-C) |
17 |
> |
18 |
> Correct, --unmerge will remove a package without considering |
19 |
> dependencies (give or take a few special cases). It is usually (or, at |
20 |
> least, should generally be) reserved for those taking a hammer to a |
21 |
> problem or with a particular desire to recover a broken system. |
22 |
> |
23 |
> Again, it's doing exactly what it's supposed to - removing a package |
24 |
> you've told it to remove (unless it's one of the few |
25 |
> almost-always-critical packages). |
26 |
|
27 |
Yes and if you see bug. All I am saying is adding warnings when someone |
28 |
goes to remove a dependency. Since a dependency IS a critical package :) |
29 |
|
30 |
Add warning message when -C/--unmerge a dependency like system, |
31 |
profile, and set files. |
32 |
https://bugs.gentoo.org/show_bug.cgi?id=624630 |
33 |
|
34 |
|
35 |
-- |
36 |
William L. Thomson Jr. |