[softwaremgmt] patch updates vs. package updates with zypper ('up' vs. 'up -t package')
Hi, you must have heard or you are one of the people complaining about the unintuitivness of 'zypper up' and 'zypper lu'. It deafults to patches (-t patch) and if you want to update package-wise, you need to add '-t package' to the command. There is a good reason for the patch as the default: people using the official release repositories and the official update repository need no more than 'zypper up' to keep their systems patched with security and other important fixes. But a lot of people also use other repositories and also want to do the updates package-wise (according to available versions of packages). Currently they have to use 'zypper up -t package'. Which is really not straightforward. (plus there are some issues with this command for which i will start a separate thread here). There were a few suggestions how to solve this. 1) use different commands for patch updates and package updates e.g. update (up) - do package-wise update list-updates(lu) - list available package udpates patch-update (pu) - do patch-wise update patch-list (pl) - list needed patches (note that we already have 'patches' command which lists _all_ available patches. We could also add an --needed option to this command to limit the list to needed patches only, instead of creating another command. 2) make -t package the default 3) make lu/up use both '-t package -t patch' 4) live with status quo Speaking for myself, i really like #1. Any other ideas? Votes? --------------------- Oh, and there is also 'zypper up $packagename'. This currently wants to install $packagename patch. To update the package, you have to do 'zypper up -t package $packagename'. Again, solution #1 from above would solve also this. But here is also question whether 'zypper patch-update foo' should install the patch named foo or install a patch for package foo. I'd vote for the latter. I think that's it for this issue. cheers, jano https://bugzilla.novell.com/show_bug.cgi?id=385990 https://bugzilla.novell.com/show_bug.cgi?id=404430 https://bugzilla.novell.com/show_bug.cgi?id=395480 + many more -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
* Jano Kupec
Hi,
you must have heard or you are one of the people complaining about the unintuitivness of 'zypper up' and 'zypper lu'. It deafults to patches (-t patch) and if you want to update package-wise, you need to add '-t package' to the command.
There is a good reason for the patch as the default: people using the official release repositories and the official update repository need no more than 'zypper up' to keep their systems patched with security and other important fixes.
The concept of treating 'update by patch' and 'update by package' differently is flawed. Starting with openSUSE 11.0, all updates are provided by packages. Patches, being created from the data available in updateinfo.xml, just enrich package updates with additional information like - severity/urgency (i.e. immediate, soon, as-needed, ...) - reason (i.e. security, data-loss, enhancement, ...) - grouping (i.e. show updates to libfoo, libfoo-devel and libfoo-32bit as one) - ordering (i.e. install libzypp updates first) - documentation So the difference between 'by patch' and 'by package' should only be in the user interface but not in the semantics.
1) use different commands for patch updates and package updates e.g.
update (up) - do package-wise update list-updates(lu) - list available package udpates patch-update (pu) - do patch-wise update patch-list (pl) - list needed patches (note that we already have 'patches' command which lists _all_ available patches. We could also add an --needed option to this command to limit the list to needed patches only, instead of creating another command.
package-wise and patch-wise schouldn't be different commands, but a qualifier for the 'list updates' command. Users might have a ~/zypper.conf file setting the default view. Klaus -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
participants (2)
-
Jano Kupec -
Klaus Kaempf