Bug 1398699 - dnf search is not user friendly
Summary: dnf search is not user friendly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-25 15:56 UTC by Honza Brázdil
Modified: 2016-11-28 10:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-28 10:05:49 UTC
Type: Bug


Attachments (Terms of Use)

Description Honza Brázdil 2016-11-25 15:56:48 UTC
Description of problem:
When I do: `dnf search python` requests I get over 5000 lines of output, that I need to scroll through to find what I'm looking for (what was actually just python-requests)

Version-Release number of selected component (if applicable):
1.1.10

How reproducible:
always

Steps to Reproduce:
1. dnf search python requests
2. get your terminal overflowed with text

Actual results:
Over 5000 results with weird ordering and grouping.

Expected results:
List of several most relevant results (max tenths of results), maybe the most relevant at the bottom.

Comment 1 Michael Mráka 2016-11-28 10:05:49 UTC
 dnf search python requests

actually searches for "python or requests". So

 dnf search requests

would gave you (less and) more relevant answers.
The weird ordering is "best match first".
As described above we don't consider current behaviour a bug.

Comment 2 Honza Brázdil 2016-11-28 10:35:42 UTC
So how would one search for "python and requests"?

And if I search e.g. for "python", I get again over 5000 results. I can see that the results are oreded in several 'groups' (I think name&description, name, description) but in each group ordered by length of the matched fields. How is e.g. length of descritpion field linked to relevance?


Note You need to log in before you can comment on or make changes to this bug.