On 08/01/2013 12:16 PM, Elias Persson wrote:
> 
> All the more reason to read up on the differences, and if it's
> only one system 'yum remove yum-autoupdate' is hardly a big deal.
> If it's 1200 systems, what difference would an option in anaconda
> make? It's not like you'll be stepping through that hundreds of
> times, right?

No, when I have to migrate to a new OS (which won't be a 6.4 derivative,
it will be a 7.0 one, so probably 8-9 months from now), then I'll worry
about the differences. When I'm testing a piece of hardware that
requires a specific kernel release on an OS I don't run, whether a new
option is installed by default or not is not on the top of my list of
things to worry about.

> My point is, what you want (the issue being highlighted) is
> already being done. It's not being done precisely where you want
> it to be done, but I don't see how that's an issue, given the
> circumstances.

What I think should be done is it be an obvious option, not hidden in
release notes.

> One could argue that yum-autoupdate isn't needed to begin with,
> what with yum-cron being available from TUV, but that's a
> different issue (and would still require at least a tweak to
> get it set up by default).

I do think that's true. yum-cron has a chkconfig option, so it's an
obvious thing to turn on and off. And to have it on by default would be
very easy.