[Yum-devel] [PATCH 1/4] Adds the commands section to the configuration file.

[James Antill]

On Mon, 2012-07-23 at 14:10 -0400, Nick Jacek wrote:
> ---
>  new-yum-cron/yum-cron.conf | 2 +-
>  new-yum-cron/yum-cron.py   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/new-yum-cron/yum-cron.conf b/new-yum-cron/yum-cron.conf
> index 3a7d690..94dfc76 100644
> --- a/new-yum-cron/yum-cron.conf
> +++ b/new-yum-cron/yum-cron.conf
> @@ -1,4 +1,4 @@
> -[main]
> +[commands]
>  # Whether a message should emitted when updates are available.
>  update_messages = yes

 So the full list here is:

+# send messages that updates are available
+update_messages = yes
+# automatically download updates
+download_updates = no
+# automatically download deps of updates
+download_deps = no
+# automatically install updates
+install_updates = no

...but now you are splitting "configuration" from "commands" you want to
look at these and where they'd go. Eg. Is. "download_deps" really a
command for "download_updates_with_deps" or more like a configuration
setting for "resolve download and also download any deps." (which would
apply to future "group upgrade" or "security upgrade" commands). I'd
assume the later. Might even be worth just removing the option entirely
(as I've no idea what use a download_updates without resolving would
be).
 Dito. "update_messages", although that's less clear and is more likely
a command.