| 1 |
On Mon, 10 Jul 2017 14:39:00 -0500 |
| 2 |
Ben Kohler <bkohler@×××××.com> wrote: |
| 3 |
> |
| 4 |
> > You aren't taking the time to read your own emerge output. |
| 5 |
|
| 6 |
It always says that same generic message. If that is the case, then why |
| 7 |
even have that option? Why not default to that all the time? Why did |
| 8 |
someone give that option + warning vs preventing it in the first place? |
| 9 |
|
| 10 |
> Now, both of these recommend --pretend, but you can use --ask with |
| 11 |
> it, for a safe unmerge that checks for reverse deps THEN allows you |
| 12 |
> to continue only if it's safe. |
| 13 |
|
| 14 |
It does not matter. I am showing you with -C it generates a warning on |
| 15 |
profile and set packages. It does not generate any sort of warning for |
| 16 |
deps or packages no in world. |
| 17 |
|
| 18 |
It is the warnings that should exist. |
| 19 |
|
| 20 |
> Try "emerge -cav gcc. |
| 21 |
|
| 22 |
That shows what its pulled in. But no message saying it will not remove |
| 23 |
because it is a dependency. |
| 24 |
|
| 25 |
Again this is about informing the user. Both ways leave the user |
| 26 |
wanting. |
| 27 |
|
| 28 |
- The -c option should say why it will not remove. |
| 29 |
- The -C option should warn like it does with profile packages |
| 30 |
|
| 31 |
-- |
| 32 |
William L. Thomson Jr. |
Archives