3
\page pg_zypp-solv-vendorchange Solver - Vendor protection
5
\author Michael Andres <ma@suse.de>
7
\section zypp-solv-vendorchange Vendor protection rule
9
Tracing a packages origin \c libzypp uses the packages \c vendor string. The \c vendor string is part of the rpm header and thus defined at the time the package was built. It stays the same, no matter which repository was used to ship the package. Using \c rpm is one way to retrieve a packages \c vendor string:
12
$ rpm -q --qf '%{name} \tvendor: %{vendor}\n' libzypp nautilus libdvdread3
13
libzypp vendor: openSUSE
14
nautilus vendor: obs://build.opensuse.org/GNOME
15
libdvdread3 vendor: http://packman.links2linux.de
18
Also several \c zypper commands will display a packages \c vendor:
23
Information for package libzypp:
25
Repository: openSUSE-11.4-Update
32
Installed Size: 7.0 MiB
33
Summary: Package, Patch, Pattern, and Product Management
35
Package, Patch, Pattern, and Product Management
38
\subsection zypp-solv-vendorchange-rule The vendor protection rule is quite simple:
40
\note When looking for an installed packages \e update \e candidate, we are looking for a package originated by the \e same \e vendor (not repository!) as the \e installed one.
43
\section zypp-solv-vendorchange-tune Vendor protection tuning
45
The \e brute \e force method is to turn off all vendor protection in \c /etc/zypp/zypp.conf:
49
## EXPERTS ONLY: Per default the solver will not replace packages of
50
## different vendors, unless you explicitly ask to do so. Setting this
51
## option to TRUE will disable this vendor check (unless the application
52
## explicitly re-enables it). Packages will then be considered based on
53
## repository priority and version only. This may easily damage your system.
55
## CHANGING THE DEFAULT IS NOT RECOMMENDED.
57
## Valid values: boolean
58
## Default value: false
60
solver.allowVendorChange = true
63
\subsection zypp-solv-vendorchange-equiv Groups of equivalent vendor strings
65
A built in example for this are the \c vendor strings for \c SuSE and \c openSUSE. All vendor strings starting (case insensitive) with either \c "suse" or \c "opensuse", are considered to be the \e same \e vendor and their packages may replace each other without asking.
67
You may define your own classes of equivalent \c vendor strings by creating an entry in the \c /etc/zypp/vendors.d directory. The directory does not exist per default, so you may have to create it first. For each group of \c vendor strings create a file, name it as you like, with the following content:
71
## A comma separated list of vendor string (prefixes!)
72
## Example: suse,opensuse
73
vendors = <PUT YOUR LIST HERE>
76
\note The built in rule unifying \c "suse" and \c "opensuse" gets disabled as soon as you mention either of those string in a custom rule.
79
\section zypp-solv-vendorchange-Impl Related classes
81
\li \ref zypp::VendorAttr (vendor string equivalence and \c vendors.d parser)
b'\\ No newline at end of file'