* Michael Schroeder <mls@suse.de> [Feb 09. 2012 18:29]:
On Thu, Feb 09, 2012 at 06:02:34PM +0100, Michael Schroeder wrote:
On Thu, Feb 09, 2012 at 05:39:59PM +0100, Klaus Kaempf wrote:
IMHO, "all" should be the default, since selective patch installation is something for the more experienced (who should be able to adapt zypper.conf ;-))
You're joking, right? Why do we release optional updates at all if they are installed anyway? (And it's just zypper, YaST/packagekit honors the optional flag, right?)
Let me rephrase this:
The defaults of 'zypper patch' and 'zypper pchk' should be so that people can put them into a cron job to keep their system in an supported state.
Thats exactly the scenario _experienced_ admins will deploy.
The maintenance team uses optional patches when they think the update is not useful for most users.
If a patch is not applicable for most users, it shouldn't be released in the first place. And if, then as a PTF (problem temporary fix == customer specific)
The idea of optional patches is exactly that they are not installed by default (i.e. in a cron job), but with a deliberate decision from the sysadmin.
My understanding of 'optional' is different: Not strictly required to be in a 'maintained' state but safe to apply anyways. Regards, Klaus --- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org