Bug 182712 - yum "do what I asked" option
Summary: yum "do what I asked" option
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-24 08:32 UTC by Need Real Name
Modified: 2014-01-21 22:53 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-24 12:52:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2006-02-24 08:32:45 UTC
It would be good if yum had an option to run, as long as no other packages would
be installed (similar to apt's behaviour).

For example, if mutt has no dependencies
# yum install mutt
would install mutt without asking me if it's okay.
It is okay, because it's going to do exactly what I told it to do.

If installing mutt would pull in another package, then a prompt is not exactly
what I've asked, so it should prompt me.

Comment 1 Seth Vidal 2006-02-24 12:52:53 UTC
from man yum.conf:
       alwaysprompt
              Either  â1â or â0â. Without this option, yum will not prompt for
              confirmation when the list of packages to be  installed  exactly
              matches  those  given  on  the command line. Unless assumeyes is
              enabled, it will still prompt for package removal, or when addi-
              tional  packages  need  to be installed to fulfill dependencies.
              Default is â1â.



Comment 2 Need Real Name 2006-02-24 17:19:19 UTC
Thanks for this. I'll use it.

The other unix commands do what I tell them, even if it's a bad thing (e.g. mv
/usr /tmp/usr).
Can I ask why it isn't the default?

Comment 3 Seth Vidal 2006-02-24 18:49:21 UTC
I've answered this question, in detail, on the yum-devel list.

short version is this: computer programs should act predictably. Prompting
'sometimes' is not predictable.

I really don't want to rehash it here.



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