On 8/10/19 1:30 PM, Tim via users wrote:
Tim:
>> If you do "dnf search all pgp" the search goes beyond just the
>> name. But you'd still want to do a search for gnupg, as well.
>> Maybe gpg, too.
Ed Greshko:
> Well, sadly....
>
> [egreshko@meimei ~]$ dnf search all pgp | grep geany
> [egreshko@meimei ~]$
> [egreshko@meimei ~]$ dnf search all gpg | grep geany
> [egreshko@meimei ~]$
>
> So nothing would have come from it.
But, if you search for gnupg, it does. Of course, you need to know
about that permutation of pgp-related things. I only do because I've
used something the past that was named that way. In my opinion, gpg-
and pgp- related packages need both those keywords in their metadata
(that could be a bugzilla report).
Sure, if one knew they should also have to check gnupg. You had suggested 2
possibilities, and I was just indicating that they would have come up empty. This would
leave one unfamiliar with the other permutations no closer to finding what they wanted.
> Then again one could have done "dnf search geany" and
scanned the
> results. Or made a guess and did
> "dnf search geany | grep encr".
In this case (geany), you would have to have known about an obscurely
related package, in the first place. Though a generic search against a
keyword like encrypt is a fair expectation.
I don't feel "obscurity" comes into play here. The poster is looking for
something
specific to geany and encryption. Doing a "dnf search geany" would have yielded
a bunch
of results of which 19 are "plugins" and the question was
"Where did you find a pgp plugin for Geany? " So, a simple search by eye would
have
revealed it.