 A zypper info command showing information of libzypp | |
| Initial release | January 14, 2006; 19 years ago (2006-01-14)[1] |
|---|---|
| Stable release | |
| Repository | https://github.com/openSUSE/libzypp  https://github.com/openSUSE/zypper |
| Written in | |
| Operating system | Linux |
| Type | Package manager |
| License | GNU General Public License |
| Website | en |
ZYpp (orlibzypp;"Zen / YaST Packages Patches Patterns Products"[6]) is apackage manager engine that powers Linux applications likeYaST, Zypper and the implementation ofPackageKit foropenSUSE andSUSE Linux Enterprise.[7] Unlike some more basic package managers, it provides asatisfiability solver to compute package dependencies.[8] It is afree and open-source software project sponsored bySUSE and licensed under the terms of theGNU General Public License v2 or later. ZYpp is implemented mostly in the programming languageC++.
Zypper is the nativecommand-line interface of the ZYpppackage manager to install, remove, update and query software packages of local or remote (networked) media. Its graphical equivalent is theYaST package manager module. It has been used inopenSUSE since version 10.2 beta1. In openSUSE 11.1, Zypper reached version 1.0. On June 2, 2009, Ark Linux announced that it has completed its review of dependency solvers and has chosen ZYpp and its tools to replace the agingAPT-RPM,[9] as the first distribution to do so. Zypper is also part of the mobile Linux distributionsMeeGo,Sailfish OS, andTizen.
zypper dup, showing available updates to installFollowing its consecutive acquisitions ofXimian and SuSE GmbH in 2003,Novell decided to merge both package management systems,YaST package manager andRed Carpet, in a best of breed approach, as the two solutions so far were used at Novell. Looking at the extant open source tools and their maturity available back in 2005, none fulfilled the requirements, and were able to work smoothly with the extant Linux management infrastructure software developed by Ximian and SUSE, so it was decided to get the best ideas from extant pieces and to work on a new implementation. Libzypp, the resulting library, was planned to be the software management engine of the SUSE distributions and the Linux Management component of theNovell ZENworks Management suite.
The Libzypp's solver was a port from the Red Carpet solver, which was written to update packages in installed systems. Using it for the full installing process brought it to its limits, and adding extensions such as support for weak dependencies and patches made it fragile and unpredictable.[10] Although this first version of ZYpp's solver worked satisfactorily, on the company enterprise products with the coupled ZMD daemon, it led to an openSUSE 10.1 release which came out in May 2006 with a system package not working as expected. In December 2006, the openSUSE 10.2 release corrected some defects of the prior release, using the revisited ZYpp v2. ZMD was subsequently removed from the 10.3 release and reserved for only the company Enterprise products. While ZYpp v3 provided openSUSE with a relatively good package manager, equivalent to other existing package managers, it suffered from some flaws in its implementation which greatly limited its speed performance.
An area where libzypp needed improvement was the speed of the dependency solver. libsolv is being written and released under therevised BSD license.[11]
Projects like Optimal Package Install/Uninstall Manager (OPIUM)[12][13] and MANCOOSI[14] were trying to fix dependency solving issues with aSAT solver. Traditional solvers likeAdvanced Packaging Tool (APT) sometimes show unacceptable deficiencies. It was decided to integrate SAT algorithms into the ZYpp stack; the solver algorithms used were based on the popular minisat solver.[15]
The SAT solver implementation as it appears in openSUSE 11.0 is based on two major, but independent, blocks:
After several months of work, the benchmark results of this fourth ZYpp version integrated with the SAT solver were more than encouraging, moving YaST and Zypper ahead of other RPM-based package managers in speed and size.[16][17]
{{citation}}: CS1 maint: numeric names: authors list (link)
| dpkg | |
|---|---|
| RPM | |
| Embedded systems |
|
| Distribution-agnostic | |
| Others (binary) | |
| Others (source) | |
| Front-ends | |
| Related topics | |
| |
| People |  | ||||
|---|---|---|---|---|---|
| Products |
| ||||
| Related | |||||
