| 1 |
On 12/07/17 14:43, William L. Thomson Jr. wrote: |
| 2 |
>>> It is not the same as -C, which is remove a package directly. |
| 3 |
>>> |
| 4 |
>>> --unmerge (-C) |
| 5 |
>> Correct, --unmerge will remove a package without considering |
| 6 |
>> dependencies (give or take a few special cases). It is usually (or, at |
| 7 |
>> least, should generally be) reserved for those taking a hammer to a |
| 8 |
>> problem or with a particular desire to recover a broken system. |
| 9 |
>> |
| 10 |
>> Again, it's doing exactly what it's supposed to - removing a package |
| 11 |
>> you've told it to remove (unless it's one of the few |
| 12 |
>> almost-always-critical packages). |
| 13 |
> Yes and if you see bug. All I am saying is adding warnings when someone |
| 14 |
> goes to remove a dependency. Since a dependency IS a critical package :) |
| 15 |
> |
| 16 |
> Add warning message when -C/--unmerge a dependency like system, |
| 17 |
> profile, and set files. |
| 18 |
> https://bugs.gentoo.org/show_bug.cgi?id=624630 |
| 19 |
|
| 20 |
My point was that --unmerge is not intended to be dependency-aware. |
| 21 |
--depclean is. As far as I can tell, that is the point others have been |
| 22 |
trying to make as well, when pointing out the differences between -c and -C. |
| 23 |
|
| 24 |
-- |
| 25 |
Sam Jorna (wraeth) |
| 26 |
GnuPG ID: D6180C26 |
Archives