Mailinglist Archive: zypp-devel (16 mails)
| < Previous | Next > |
Re: [zypp-devel] RFC - Bug 737843 - zypper patch installs optional patches
- From: Jiri Srain <jsrain@xxxxxxx>
- Date: Fri, 10 Feb 2012 08:03:48 +0100
- Message-id: <1358288.xyxcN1CE1v@tullamore.suse.cz>
Dne Čt 9. února 2012 20:05:49, Klaus Kaempf napsal(a):
Well, we used to use patches to drag in some proprietary stuff (fonts, gfx
drivers). I see optional patches more like bringing new features.
To have a real-life example for SLES11-SP1: We ship as a patch the DUD which
adds support for update via AutoYaST (it effectively brings a new package
which contains the DUD). It is completely useless to install this patch on any
SLES11-SP1 box; what you need to do is to get the DUD once and use it to
update the installation environment.
Jiri
Regards,
Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: jsrain@xxxxxxx
Lihovarska 1060/12 tel: +420 284 084 659
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.cz
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: zypp-devel+owner@xxxxxxxxxxxx
* Michael Schroeder <mls@xxxxxxx> [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.
Well, we used to use patches to drag in some proprietary stuff (fonts, gfx
drivers). I see optional patches more like bringing new features.
To have a real-life example for SLES11-SP1: We ship as a patch the DUD which
adds support for update via AutoYaST (it effectively brings a new package
which contains the DUD). It is completely useless to install this patch on any
SLES11-SP1 box; what you need to do is to get the DUD once and use it to
update the installation environment.
Jiri
--
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
Regards,
Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: jsrain@xxxxxxx
Lihovarska 1060/12 tel: +420 284 084 659
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.cz
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: zypp-devel+owner@xxxxxxxxxxxx
| < Previous | Next > |