On Mon, 10 Jul 2017 17:08:54 -0500 Ben Kohler <bkoh...@gmail.com> wrote:
> On Mon, Jul 10, 2017 at 4:42 PM, William L. Thomson Jr.
> <wlt...@o-sinc.com> wrote:
>
> >
> > If people understood, then saying use -c or -C makes no sense. It
> > does not address the lack of output from either I am talking about.
> >
> > --
> > William L. Thomson Jr.
> >
> I really thought I understood you in that you wanted true reverse
> dependencies calculated, to check against that, and warn for it.
You are correct in that. Which the -c option already does. It just does
not tell you why it did not remove a package. When you add -v/verbose.
It shows you the deps, or some. But it does not tell you it will not
remove because those packages depend on it. Seems obvious, but if you
did not use -v/verbose. You do not see those deps, and just have to
assume. Even when the deps are shown. The user must assume the package
was not removed due to deps, because its not saying explicitly.
It is not changing anything with the -c option. Other than generating
some additional generic text for the user as part of its current output
and function. With package A being the one they are trying to remove.
The rest would be boiler plate
"Package ${PN} not removed due to dependencies"
> I think that you are actually talking about a warning upon forced
> unmerge of anything not in /var/lib/portage/world, is that correct?
That is also correct. Its two fold.
- If using -c, the deps are known, or at least some, and takes time.
The output just needs to say will not remove because of deps. Not
specifically what deps. It could in theory stop on the first
encountered to save time, and only go further if -v is specified.
Which it may now I have not looked at the code.
- If using -C it should at minimum check if the package is in
world/user installed, and say something otherwise.
That part does not require it to resolve deps. Just check world file,
assuming its correct. Though could be thrown off if say gcc, or another
was in the world file. I think the profile or set would catch that as
it does now and generate a warning, regardless.
Now in the case of no world file, or something, they maybe revert back
to some of the behavior of -c. with -C. But I would think if no world
file, or packages in world. Then the user did not emerge anything or
nuked that file.
The -C option already seems to check say a profile and set file.
Otherwise how would it know that package was in either. Seems the same
could be done for a package not in either of those files, or world. To
warn, your removing a package you did not install.
I will file 2 bugs, that should be straight forward and clear.
--
William L. Thomson Jr.
pgpOj7xSdj0TL.pgp
Description: OpenPGP digital signature
