On Mon, 10 Jul 2017 14:39:00 -0500 Ben Kohler <bkoh...@gmail.com> wrote: > > > You aren't taking the time to read your own emerge output.
It always says that same generic message. If that is the case, then why even have that option? Why not default to that all the time? Why did someone give that option + warning vs preventing it in the first place? > Now, both of these recommend --pretend, but you can use --ask with > it, for a safe unmerge that checks for reverse deps THEN allows you > to continue only if it's safe. It does not matter. I am showing you with -C it generates a warning on profile and set packages. It does not generate any sort of warning for deps or packages no in world. It is the warnings that should exist. > Try "emerge -cav gcc. That shows what its pulled in. But no message saying it will not remove because it is a dependency. Again this is about informing the user. Both ways leave the user wanting. - The -c option should say why it will not remove. - The -C option should warn like it does with profile packages -- William L. Thomson Jr.
pgp5TMEgVbvWZ.pgp
Description: OpenPGP digital signature
