Bug 366261 - yum is only partially case-insensitive and therefore inconsistent
yum is only partially case-insensitive and therefore inconsistent
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jeremy Katz
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-04 19:32 EST by Roland Wolters
Modified: 2014-01-21 18:00 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-04 20:35:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Roland Wolters 2007-11-04 19:32:06 EST
Description of problem:
Depending on the action yum is sometimes case sensitive and sometimes 
in-sensitive. This is inconsistent and should be fixed to a state where yum is 
either case in-sensitive in all cases or has a flag to be in-sensitive.

How reproducible:
'yum info policykit' and 'yum search policykit' show information about the 
package PolicyKit, 'yum install policykit' or 'yum provides policykit' however 
both don't show any results.
The inconsistency is annoying and confusing. Also, the fact that the 'install' 
and 'update' update options both are case sensitive is annoying by itself. 
There are too many packages where a user simply can't know if there are 
capital letters or not.
Comment 1 Seth Vidal 2007-11-04 20:35:22 EST
That is, in fact on purpose.

When you're searching for something you want to be as lax as possible about what
you accept so the user can find _something_.

when asked to take an action which will modify the system it's important to be
strict about what you accept so you don't accidentally do things that are unwanted.

search/info/list are types of searching - so case insensitive
install/update/remove are all system-modifying actions - case sensitive.

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