Description of problem: Making Rpmdrake easier will help end-users to install packages easily. Adding the package icon and the application name (alongside the package name) will make it easier.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=28499
Rpmdrake is quite good. Can you explain what it is that you find difficult? Do not package names give the application name? Have you found examples of where an application's name is not evident from the package name? If a particumllar package name is not helpful, that can be bugged. Icons only apply to GUI applications anyway - a minority. In short, please enlarge on what you have in mind; particularly, a better explanation of how you see rpmdrake as not making life easy for users.
Source RPM: (none) => rpmdrake-6.32-1.mga8.src.rpmCC: (none) => lewyssmithStatus: NEW => NEEDINFO
(In reply to Lewis Smith from comment #1) > Rpmdrake is quite good. Can you explain what it is that you find difficult? > Do not package names give the application name? Have you found examples of > where an application's name is not evident from the package name? If a > particumllar package name is not helpful, that can be bugged. > Icons only apply to GUI applications anyway - a minority. > In short, please enlarge on what you have in mind; particularly, a better > explanation of how you see rpmdrake as not making life easy for users. Rpmdrake is good, but is difficult for end-users. End-users do not know what is a "software package", and even the easiest package managers are "expert tasks" (this was my experience when I used Linux for the first times, this may be the experience of more end-users). The end-users search for an "application" and not for a "package", so they will not find calligra-words, for example, if they will type "Calligra Words". The improvement I suggest is to: 1. Add the application name before the package name and put the package name in parentheses. 2. Add the package icon to the left of the application name. 3. Make the package list less-compact. 4. Enable searching by the application name.
Thank you for the fuller explanation. I just tried 'calligra' alone, and saw both the complete suite and the individual bits including Words. That is one of the nice things about rpmdrake: if you search vaguely, you get results which you can peruse. A few libs are also shown (sometimes many), but no naive user would bother selecting things like that which mean nothing to him. I tried your "calligra words" also, and that came up trumps. When looking by category, 'suites' shows calligra; 'word processors' shows calligra-words. It is difficult to imagine how any user could be confused by this, given that any package manager demands some familiarity with its use. I think the request is too subtle, but am passing it to the MageiaTools team for their judgement. They might agree with you.
Status: NEEDINFO => NEWAssignee: bugsquad => mageiatoolsCC: lewyssmith => (none)
(In reply to Omer I.S. from comment #2) > (In reply to Lewis Smith from comment #1) > > Rpmdrake is quite good. Can you explain what it is that you find difficult? > > Do not package names give the application name? Have you found examples of > > where an application's name is not evident from the package name? If a > > particumllar package name is not helpful, that can be bugged. > > Icons only apply to GUI applications anyway - a minority. > > In short, please enlarge on what you have in mind; particularly, a better > > explanation of how you see rpmdrake as not making life easy for users. > > Rpmdrake is good, but is difficult for end-users. End-users do not know what > is a "software package", and even the easiest package managers are "expert > tasks" (this was my experience when I used Linux for the first times, this > may be the experience of more end-users). The end-users search for an > "application" and not for a "package", so they will not find calligra-words, > for example, if they will type "Calligra Words". > The improvement I suggest is to: > 1. Add the application name before the package name and put the package name > in parentheses. > 2. Add the package icon to the left of the application name. > 3. Make the package list less-compact. > 4. Enable searching by the application name. I am sorry for my English and will try to explain it better. End-users search for the application name and not for the package name. So, if they search for "Calligra Words" they will not find "calligra-words" because they used space and did not use a hyphen. Adding the package icon can improve the package manager looking and make it easier for the end-users. My idea is to transform: package-name Into: [icon] Application Name (package-name) And to enable searching by the application name (with spaces).
It actually works when you search "calligra words" (with space) that ALL related Calligra packages including Words show up, as already said by Lewis. It is already easy for end users. And icons are no real help if you search for a package/software.
Created attachment 12551 [details] Search results
CC: (none) => sturm-fr
CC: sturm-fr => (none)
Closing as unconfirmed. This idea was an alternative to add Discover or GNOME Software, but is not as good as the said solution for end-users.
Ever confirmed: 1 => 0Status: NEW => UNCONFIRMED
(In reply to Omer I.S. from comment #7) > Closing as unconfirmed. This idea was an alternative to add Discover or > GNOME Software, but is not as good as the said solution for end-users. You want this to be closed. Feel free to reopen.
Status: UNCONFIRMED => RESOLVEDCC: (none) => ouaurelienResolution: (none) => INVALID
I think the original complaint had to do with the way rpmdrake searched on what it was given (not excluding special characters like "-"), but this seems to have been addressed. However, under the original subject, there are ways rpmdrake could be improved. Specifically, when searching by filename, the results only show packages which have matching filenames, which is fine. However, if you explode the Files category for each of the results, you can get thousands of files with no way to search for the file you wanted. Doing such a search for the wanted file on every result selection can be prohibitive. It would be helpful if a filename search attached the filenames which matched the search to a subset of files that could be incorporated into a tooltip for the display of the result package in the upper display. That way, a user searching for a specific or partial filename could do a mouseover to quickly decide whether a result package did or did not meet his actual requirements. If you'd like, I can put this in a separate enhancement request, but the title for this bug was so generic, I thought I'd try it here.
Ever confirmed: 0 => 1CC: (none) => ftgResolution: INVALID => (none)Status: RESOLVED => REOPENED
CC: (none) => omeritzicschwartz