On 2023.09.21 13:09, Alan McKinnon wrote:
On Thu, Sep 21, 2023 at 6:35 PM Jack <ostrof...@users.sourceforge.net>
wrote:
> On 9/21/23 12:30, Alan McKinnon wrote:
>
>
>
> On Thu, Sep 21, 2023 at 5:03 PM Neil Bothwick <n...@digimed.co.uk>
wrote:
>
>> On Thu, 21 Sep 2023 13:45:19 +0200, Alan McKinnon wrote:
>>
>> > Not 100% back in the gentoo groove yet, forget some basic tools.
>> > Something pulled in ruby, I know not what.
>> > What commands show me what installed packages have ruby as a
dependency?
>>
>> emerge -cav ruby
>
> but that is the wrong way wrong.
>
Why do you think so? Trying to remove ruby will tell you why
portage refuses to do so, and that reason is any installed packages
that depend on it. This differs from using equery, which will tell
you every package that depends on ruby, whether or not it is
installed. Using -d instead of -a saves you from typing "N" just in
case it IS willing to unmerge it.
>
Because I wanted to know, recursively, what packages depended on
ruby, i.e. I have ruby (which I despise) so why?
The answer is kdenlive which I can see in equery d, and cannot see in
emerge -c
What options did you give to equery?
I had thought that "equery d" listed only direct dependencies, and that
it listed packages whether installed or not. Actually reading the fine
equery man page, under the section on "depends (d)" are the options
-a, --all packages - Include dependencies that are not installed. This
can take a while.
-D, --indirect - Search for both direct and indirect dependencies
so I was wrong on both counts. I can imagine using -D might give a
large list, but probably not so bad, as long as you don;t us both -a
and -D. Is this where you found kdenlive?
This matters because emerge -avc only gives immediate dependencies, I
wanted to see the full dep tree
--
Alan McKinnon
alan dot mckinnon at gmail dot com
