Bug 151704 - yum doesn't use standard command line parser?
Summary: yum doesn't use standard command line parser?
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-21 19:50 UTC by Need Real Name
Modified: 2014-01-21 22:51 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2005-03-22 18:58:58 UTC


Attachments (Terms of Use)

Description Need Real Name 2005-03-21 19:50:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050313 Epiphany/1.5.8

Description of problem:
yum doesn't allow the generous (and intuitive) parsing of command line arguments which other programs allow.

For example, yum -y update --exclude="openoffice*" fails completely.
yum -y --exclude="openoffice*" update works.

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


How reproducible:
Always

Steps to Reproduce:
x

Additional info:

Comment 1 Seth Vidal 2005-03-22 18:58:58 UTC
The problem is that for pkg names it's impossible to separate them out.

remember a package name could easily be

--exclude=*foo*

so yum can't know any different.


Comment 2 Need Real Name 2005-03-22 19:07:40 UTC
Why is --exclude=*foo* a problem? It doesn't begin with a hyphen..

Comment 3 Seth Vidal 2005-03-22 19:10:59 UTC
everything coming AFTER the command is considered an argument, not an option/flag

--option/-flag command arg arg arg

so if you have:
-y update --exclude=foo --exclude=bar

then yum will think:
update --exclude=foo --exclude=bar

and fail to find those items available for update, ie: it's looking for pkgs named:
 --exclude=foo and --exclude=bar

do see what I'm saying?

Comment 4 Need Real Name 2005-03-22 19:14:52 UTC
Yes, and that's the bug. It's less flexible with command line arguments that
other programs.


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