On 02/08/13 02:26, Vincent Liggio wrote:
> 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.

If you really do have 1200 systems to worry about, I'd be looking at 
things like satellite. I have ~20-25 systems and yum-autoupdate is 
fantastic. It does what it says on the box and relieves me of having to 
watch / check for updates every day. I get an email in the morning that 
tells me what was updated and if there were any problems.

I've been doing this for several years with no problems. Before 
yum-autoupdate I had my own script do similar things in the daily cron.

>> 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.

Its hardly hidden - and if you don't like it, don't install the package 
- its purely in your control.