[Yum-devel] [PATCH 2/2] Add documentation for assumeyes change.

tim.lauridsen at gmail.com tim.lauridsen at gmail.com
Fri Jul 15 08:19:46 UTC 2011


On Tue, Jul 12, 2011 at 11:36 PM, James Antill <james at fedoraproject.org> wrote:
> On Tue, 2011-07-12 at 09:45 +0200, tim.lauridsen at gmail.com wrote:
>> On Mon, Jul 11, 2011 at 8:40 PM, James Antill <james at fedoraproject.org> wrote:
>> >  So would you use it, if we just removed the "txmbr.ts_state == 'e'"
>> > part of the conditional? Any other thoughts on how we could change it to
>> > be useful?
> [...]
>> `downgrade' - Prompt if something will be downgraded.
>> Just a special kind of upgrade, where you upgrade a current package
>> with a older version (could be handled by the upgrade flag)
>>
>> `reinstall' - Prompt if something will be reinstalled.
>> Just a special kind of upgrade (could be handled by the upgrade flag)
>
>  I don't really like saying these are just special "upgrades", in fact
> I'd probably prefer to just delete the erase line instead ... do you
> really think this will confuse people?

What is was trying to say, was that they could all be controlled by
the 'update' option, they don't need there own flag.
if the 'update' flag is on, then 'updates', 'downgrade' and reinstall
is covered by this flag.

>
>> `obsoleter' - Prompt if something will obsolete other packages.
>> Just a special kind of upgrade (could be handled by the upgrade flag)
>>
>> `obsoleted' - Prompt if something will be obsoleted.
>> Just a special kind of upgrade (could be handled by the upgrade flag)
>
>  This is fair enough, I thought people might want control of it at the
> time ... but the more I think about it the more I think you are correct.
> Obsoletes suck because it's really a flag, not a state, and atm. we
> can't easily find out what the real state is ... meh.
>
>> `_unnamed_' - Prompt if a package name is not specified on the command line.
>> It is very hard for an end user to understand this one, I see no need
>> for this option
>
>  This is what alwaysprompt does now ... I guess I could just remove
> this, but it doesn't seem that hard to explain.
>  I think maybe the idea is that if you had alwaysprompt=false, and
> "accidentally" did "yum install '*'" that would be bad, but that seems
> pretty unlikely (and I doubt it works), and we aren't changing the
> default from alwaysprompt=true atm.
>
>> `_skip_' - Prompt if a package was skipped (by --skip-broken).
>> if a user adds --skip-broken then there should always be a prompt (if
>> -y is not set)
>> So no need of an option here.
>
>  Ok, so you think we should just do:
>
>  if opts.conf.skip_broken:
>    return True
>
> ...right at the top? I have no objection to that.

That would be fine.

>
>> `_not_available_' - Prompt if a package was asked for from a repo. but
>> couldn't be found (Eg. by load-ts or history undo/redo).
>> It is very hard for an end user to understand this one, I see no need
>> for this option
>>
>> `_not_installed_' - Prompt if a package was asked for from the rpmdb
>> but couldn't be found (Eg. by load-ts or history undo/redo).
>> It is very hard for an end user to understand this one, I see no need
>> for this option
>
>  Yeh, it's probably worth just always prompting here ... I think the
> users who want to run "load-ts" with packages that can't be found and
> want no prompt are probably a pretty small group :).

Agree

Tim


More information about the Yum-devel mailing list