1 ## Configuration file for software management
4 ## Boolean values are 0 1 yes no on off true false
11 ## Override the detected architecture
13 ## Valid values: i586, i686, x86_64, ppc, ppc64, ia64, s390, s390x, ..
14 ## Default value: Autodetected
16 ## ** CAUTION: Only set if you know what you're doing !
17 ## ** Changing this needs a full refresh (incl. download)
18 ## ** of all repository data.
24 ## Path where the caches are kept.
26 ## Valid values: A directory
27 ## Default value: /var/cache/zypp
29 # cachedir = /var/cache/zypp
33 ## Path where the repo metadata is downloaded and kept.
35 ## Valid values: A directory
36 ## Default value: {cachedir}/raw
38 ## Changing this needs a full refresh (incl. download) of all repository data
40 # metadatadir = /var/cache/zypp/raw
44 ## Path where the repo solv files are created and kept.
46 ## Valid values: A directory
47 ## Default value: {cachedir}/solv
49 # solvfilesdir = /var/cache/zypp/solv
53 ## Path where the repo packages are downloaded and kept.
55 ## Valid values: A directory
56 ## Default value: {cachedir}/packages
58 # packagesdir = /var/cache/zypp/packages
62 ## Path where the configuration files are kept.
64 ## Valid values: A directory
65 ## Default value: /etc/zypp
67 # configdir = /etc/zypp
70 ## Path where the known repositories .repo files are kept
72 ## Valid values: A directory
73 ## Default value: {configdir}/repos.d
75 ## Changing this invalidates all known repositories
77 # reposdir = /etc/zypp/repos.d
80 ## Path where the known services .service files are kept
82 ## Valid values: A directory
83 ## Default value: {configdir}/services.d
85 ## Changing this invalidates all known services
87 # servicesdir = /etc/zypp/services.d
90 ## Path where custom repo variable definitions are kept
92 ## Valid values: A directory
93 ## Default value: {configdir}/vars.d
95 ## Changing this undefines all custom repo variables. Built-in
96 ## variables (like '$arch', '$basearch' or $releasever) are not
97 ## affected, but reset to their default values.
99 ## A custom repo variable is defined by creating a file inside the
100 ## directory. The variable name equals the file name. The files fist
101 ## line (up to but not including the newline character) defines the
104 # varsdir = /etc/zypp/vars.d
107 ## Whether repository urls should be probed when added
109 ## Valid values: boolean
110 ## Default value: false
112 ## If true, accessability of repositories is checked immediately (when added)
113 ## (e.g. 'zypper ar' will check immediately)
114 ## If false, accessability of repositories is checked when refreshed
115 ## (e.g. 'zypper ar' will delay the check until the next refresh)
117 # repo.add.probe = false
121 ## Amount of time in minutes that must pass before another refresh.
123 ## Valid values: Integer
126 ## If you have autorefresh enabled for a repository, it is checked for
127 ## up-to-date metadata not more often than every <repo.refresh.delay>
128 ## minutes. If an automatic request for refresh comes before <repo.refresh.delay>
129 ## minutes passed since the last check, the request is ignored.
131 ## A value of 0 means the repository will always be checked. To get the opposite
132 ## effect, disable autorefresh for your repositories.
134 ## This option has no effect for repositories with autorefresh disabled, nor for
135 ## user-requested refresh.
137 # repo.refresh.delay = 10
140 ## Translated package descriptions to download from repos.
142 ## A list of locales for which translated package descriptions should
143 ## be downloaded, in case they are availavble and the repo supports this.
144 ## Not all repo formats support downloading specific translations only.
146 ## Valid values: List of locales like 'en', 'en_US'...
147 ## Default value: RequestedLocales
149 ## If data for a specific locale are not available, we try to find some
150 ## fallback. Translations for 'en' are always downloaded.
152 # repo.refresh.locales = en, de
155 ## Maximum number of concurrent connections to use per transfer
157 ## Valid values: Integer
160 ## This setting is only used if more than one is possible
161 ## Setting it to a reasonable number avoids flooding servers
163 # download.max_concurrent_connections = 5
166 ## Sets the minimum download speed (bytes per second)
167 ## until the connection is dropped
168 ## This can be useful to prevent security attacks on hosts by
169 ## providing updates at very low speeds.
173 # download.min_download_speed = 0
175 ## Maximum download speed (bytes per second)
177 # download.max_download_speed = 0
179 ## Number of tries per download which will be
180 ## done without user interaction
181 ## 0 means no limit (use with caution)
182 # download.max_silent_tries = 5
185 ## Maximum time in seconds that you allow a transfer operation to take.
187 ## This is useful for preventing your batch jobs from hanging for hours due
188 ## to slow networks or links going down. Limiting operations to less than a
189 ## few minutes risk aborting perfectly normal operations.
191 ## Valid values: [0,3600]
192 ## Default value: 180
194 # download.transfer_timeout = 180
197 ## Whether to consider using a .delta.rpm when downloading a package
199 ## Valid values: boolean
200 ## Default value: true
202 ## Using a delta rpm will decrease the download size for package updates
203 ## since it does not contain all files of the package but only the binary
204 ## diff of changed ones. Recreating the rpm package on the local machine
205 ## is an expensive operation (memory,CPU). If your network connection is
206 ## not too slow, you benefit from disabling .delta.rpm.
208 # download.use_deltarpm = true
211 ## Whether to consider using a deltarpm even when rpm is local
213 ## Valid values: boolean
214 ## Default value: false
216 ## This option has no effect unless download.use_deltarpm is set true.
218 # download.use_deltarpm.always = false
221 ## Hint which media to prefer when installing packages (download vs. CD).
223 ## Valid values: download, volatile
224 ## Default value: download
226 ## Note that this just a hint. First of all the solver will choose the 'best'
227 ## package according to its repos priority, version and architecture. But if
228 ## there is a choice, we will prefer packages from the desired media.
230 ## Packages available locally are always preferred. The question is whether
231 ## you prefer packages being downloaded via FTP/HTTP/HTTPS (download), rather
232 ## than being prompted to insert a CD/DVD (volatile), in case they are available
235 ## Name | Priority | URI
236 ## openSUSE-11.1 99 dvd:///
237 ## openSUSE-11.1-Oss 99 http://download.opensuse.org/distribution/11.1/repo/oss
239 ## In the above example 2 repositories with similar content are used. Rather
240 ## than raising the priority of one of them to 'prefer' a certain media, you
241 ## should use the same priority for both and set download.media_preference
244 ## download.media_preference = download
247 ## Path where media are preferably mounted or downloaded
249 ## Valid values: A (writable) directory
250 ## Default value: /var/adm/mount
252 ## The media backend will try to organize media mount points and download areas
253 ## below this directory, unless a different location is requested by the application.
255 ## If the directory is not accessible and read/writable for a specific user,
256 ## the fallback is to use /var/tmp.
258 ## download.media_mountdir = /var/adm/mount
261 ## Signature checking (repo metadata and downloaded rpm packages)
263 ## boolean gpgcheck (default: on)
264 ## boolean repo_gpgcheck (default: unset -> according to gpgcheck)
265 ## boolean pkg_gpgcheck (default: unset -> according to gpgcheck)
267 ## Explicitly setting 'gpgcheck', 'repo_gpgcheck' 'pkg_gpgcheck' in a
268 ## repositories .repo file will overwrite the defaults for this specific
271 ## If 'gpgcheck' is 'on' (the default) we will check the signature of repo metadata
272 ## (packages are secured via checksum inside the metadata). Using unsigned repos
273 ## needs to be confirmed.
274 ## Packages from signed repos are accepted if their checksum matches the checksum
275 ## stated in the repo metadata.
276 ## Packages from unsigned repos need a valid gpg signature, using unsigned packages
277 ## needs to be confirmed.
279 ## The above default behavior can be tuned by explicitly setting 'repo_gpgcheck'
280 ## and/or 'pkg_gpgcheck':
282 ## 'repo_gpgcheck = on' same as the default.
284 ## 'repo_gpgcheck = off' will silently accept unsigned repos. It will NOT turn off
285 ## signature checking on the whole, nevertheless it's not a secure setting.
287 ## 'pkg_gpgcheck = on' will enforce the package signature checking and the need
288 ## to confirm unsigned packages for all repos (signed and unsigned).
290 ## 'pkg_gpgcheck = off' will silently accept unsigned packages. It will NOT turn off
291 ## signature checking on the whole, nevertheless it's not a secure setting.
293 ## If 'gpgCheck' is 'off' (not recommended), no checks are performed. You can still
294 ## enable them individually by setting 'repo_gpgcheck' and/or 'pkg_gpgcheck' to 'on'.
296 ## DISABLING GPG CHECKS IS NOT RECOMMENDED.
297 ## Signing data enables the recipient to verify that no modifications
298 ## occurred after the data were signed. Accepting data with no, wrong
299 ## or unknown signature can lead to a corrupted system and in extreme
300 ## cases even to a system compromise.
302 # repo_gpgcheck = unset -> according to gpgcheck
303 # pkg_gpgcheck = unset -> according to gpgcheck
306 ## Commit download policy to use as default.
308 ## DownloadOnly, Just download all packages to the local cache.
309 ## Do not install. Implies a dry-run.
311 ## DownloadInAdvance, First download all packages to the local cache.
312 ## Then start to install.
314 ## DownloadInHeaps, Similar to DownloadInAdvance, but try to split
315 ## the transaction into heaps, where at the end of
316 ## each heap a consistent system state is reached.
318 ## DownloadAsNeeded Alternating download and install. Packages are
319 ## cached just to avid CD/DVD hopping. This is the
320 ## traditional behaviour.
322 ## <UNSET> If a value is not set, empty or unknown, we pick
323 ## some sane default.
325 ## commit.downloadMode =
328 ## Defining directory which contains vendor description files.
330 ## Each file in this directory defines a (comma separated) list of
331 ## equivalent vendors string prefixes (case-insensitive comparision):
332 ## ------------------------- file begin -----------------------
334 ## vendors = MyVendor,AlternateName
335 ## ------------------------- file end -----------------------
336 ## By this vendor strings starting with "MyVendor" or "AlternateName"
337 ## are considered to be equivalent. Packages from equivalent vendors
338 ## may replace each other without being considered as a 'vendor change'.
340 ## Valid values: A directory
341 ## Default value: {configdir}/vendors.d
343 # vendordir = /etc/zypp/vendors.d
347 ## The solvers general attitude when resolving jobs.
351 ## Job - Focus on installing the best version of the requested packages.
352 ## Add missing dependencies as needed. This is the solvers default.
354 ## Installed - Focus on applying as little changes to the installed packages
355 ## as needed. Choosing an older version of a package is valid if
356 ## it's dependencies require less changes to the system.
358 ## Update - Focus on updating requested packages and their dependencies as
361 ## Default - If the value is not set, empty or unknown, we use the default.
366 ## Whether only required packages are installed.
368 ## Recommended packages, will not be regarded.
370 ## Valid values: boolean
371 ## Default value: false
373 # solver.onlyRequires = false
376 ## EXPERTS ONLY: Per default the solver will not replace packages of
377 ## different vendors, unless you explicitly ask to do so. Setting this
378 ## option to TRUE will disable this vendor check (unless the application
379 ## explicitly re-enables it). Packages will then be considered based on
380 ## repository priority and version only. This may easily damage your system.
382 ## Valid values: boolean
383 ## Default value: false
385 # solver.allowVendorChange = false
388 ## EXPERTS ONLY: TUNE DISTRIBUTION UPGRADE (DUP)
389 ## Set whether to allow package version downgrades upon DUP.
391 ## Valid values: boolean
392 ## Default value: true
394 # solver.dupAllowDowngrade = true
397 ## EXPERTS ONLY: TUNE DISTRIBUTION UPGRADE (DUP)
398 ## Set whether follow package renames upon DUP.
400 ## Valid values: boolean
401 ## Default value: true
403 # solver.dupAllowNameChange = true
406 ## EXPERTS ONLY: TUNE DISTRIBUTION UPGRADE (DUP)
407 ## Set whether to allow changing the packages architecture upon DUP.
409 ## Valid values: boolean
410 ## Default value: true
412 # solver.dupAllowArchChange = true
415 ## EXPERTS ONLY: TUNE DISTRIBUTION UPGRADE (DUP)
416 ## Set whether to allow changing the packages vendor upon DUP. If you
417 ## are following a continuous distribution like Tumbleweed or Factory
418 ## where you use 'zypper dup --no-allow-vendor-change' quite frequently,
419 ## you may indeed benefit from disabling the VendorChange. Packages from
420 ## OBS repos will then be kept rather than being overwritten by Tumbleweeds
423 ## Valid values: boolean
424 ## Default value: true
426 # solver.dupAllowVendorChange = true
429 ## EXPERTS ONLY: Cleanup when deleting packages. Whether the solver should
430 ## per default try to remove packages exclusively required by the ones he's
433 ## This option should be used on a case by case basis, enabled via
434 ## command line options or switches the applications offer. Changing
435 ## the global default on a system where unattended actions are performed,
436 ## may easily damage your system.
438 ## CHANGING THE DEFAULT IS NOT RECOMMENDED.
440 ## Valid values: boolean
441 ## Default value: false
443 # solver.cleandepsOnRemove = false
446 ## This file contains requirements/conflicts which fulfill the
447 ## needs of a running system.
448 ## For example the system would be broken if not glibc or kernel is
450 ## So the user will be informed if these packages will be deleted.
452 ## Format: Each line represents one dependency:
456 ## Default value: {configdir}/systemCheck
458 # solver.checkSystemFile = /etc/zypp/systemCheck
461 ## This directory can contain files that contain requirements/conflicts
462 ## which fulfill the needs of a running system (see checkSystemFile).
464 ## Files are read in alphabetical order.
466 ## Default value: {configdir}/systemCheck.d
468 # solver.checkSystemFileDir = /etc/zypp/systemCheck.d
471 ## When committing a dist upgrade (e.g. 'zypper dup') a solver testcase
472 ## is written to /var/log/updateTestcase-<date>. It is needed in bugreports.
473 ## This option returns the number of testcases to keep on the system. Old
474 ## cases will be deleted, as new ones are created.
476 ## Use 0 to write no testcase at all, or -1 to keep all testcases.
478 ## Valid values: Integer
481 # solver.upgradeTestcasesToKeep = 2
484 ## Whether dist upgrade should remove a products dropped packages.
486 ## A new product may suggest a list of old and no longer supported
487 ## packages (dropped packages). Performing a dist upgrade the solver
488 ## may try to delete them, even if they do not cause any dependency
491 ## Turning this option off, the solver will not try to remove those
492 ## packages unless they actually do cause dependency trouble. You may
493 ## do the cleanup manually, or simply leave them installed as long
494 ## as you don't need the disk space.
496 ## Valid values: Boolean
497 ## Default value: true
499 # solver.upgradeRemoveDroppedPackages = true
502 ## Packages which can be installed in different versions at the same time.
504 ## Packages are selected either by name, or by provides. In the later case
505 ## the string must start with "provides:" immediately followed by the capability.
508 ## kernel - just packages whith name 'kernel'
509 ## provides:multiversion(kernel) - all packages providing 'multiversion(kernel)'
510 ## (kenel and kmp packages should do this)
512 ## Comma separated list of packages.
517 multiversion = provides:multiversion(kernel)
520 ## Defining directory which may contain additional multiversion definitions.
522 ## If the directory exists, each file in this directory is scanned, expecting
523 ## one valid multiversion list entry per line. Empty lines and lines starting
524 ## with '#' are ignored.
525 ## ------------------------- [/etc/zypp/multiversion.d/example file begin] -----------------------
526 ## # An alternate way to enable kernel packages being
527 ## # installed in parallel:
529 ## provides:multiversion(kernel)
530 ## ------------------------- [/etc/zypp/multiversion.d/example file end] -----------------------
532 ## Valid values: A directory
533 ## Default value: {configdir}/multiversion.d
535 # multiversiondir = /etc/zypp/multiversion.d
537 ## Comma separated list of kernel packages to keep installed in parallel, if the
538 ## above multiversion variable is set. Packages can be specified as
539 ## 2.6.32.12-0.7 - Exact version to keep
540 ## latest - Keep kernel with the highest version number
541 ## latest-N - Keep kernel with the Nth highest version number
542 ## running - Keep the running kernel
543 ## oldest - Keep kernel with the lowest version number (the GA kernel)
544 ## oldest+N - Keep kernel with the Nth lowest version number
546 ## Note: This entry is not evaluated by libzypp, but by the
547 ## purge-kernels service (via /sbin/purge-kernels).
549 ## Default: Do not delete any kernels if multiversion = provides:multiversion(kernel) is set
550 multiversion.kernels = latest,latest-1,running
553 ## Path to locks file. If not exist then is create.
554 ## In this file is saved also UI locks.
556 ## valid value: path to file or place where file can be created
557 ## default value: {configdir}/locks
559 # locksfile.path = /etc/zypp/locks
562 ## Whether to apply locks in locks file after zypp start.
564 ## Valid values: boolean
565 ## Default value: true
567 # locksfile.apply = true
570 ## Where update items are stored
571 ## (example: scripts, messages)
573 ## Valid values: path to directory
574 ## Default value: /var/adm
576 # update.datadir = /var/adm
579 ## Where update messages are stored
581 ## Valid values: path to directory
582 ## Default value: {update.datadir}/update-messages
584 # update.messagesdir = /var/adm/update-messages
587 ## Where update scripts are stored
589 ## Valid values: path to directory
590 ## Default value: {update.datadir}/update-scripts
592 # update.scriptsdir = /var/adm/update-scripts
595 ## Command to be invoked to send update messages.
597 ## Packages may leave an update message file in {update.messagesdir}.
598 ## At the end of each commit, zypp collects those messages and may send
599 ## a notification to the user.
601 ## zypp will prepare the update messages according to the selected
602 ## content format and pipe the content to the command.
605 ## single - For each update message invoke the command and send
607 ## none - For each update message invoke the command but don't
608 ## use a pipe to send any data. You probably want to pass
609 ## the message file on the commandline using %P (see
611 ## digest - Single invocation of the command, sending the path
612 ## names of all update message. One per line.
613 ## bulk - Single invocation of the command, sending the
614 ## concatenated content of all update messages, separated
618 ## %p - package identification (name-version-release.arch)
619 ## %P - full path to the update message file
621 ## Valid values: The value is specified as "format | command".
622 ## An empty value will turn off any notification.
624 ## Examples: single | mail -s 'Update message from %p' root
625 ## none | my-send-script -f %P
627 ## Default value: <empty>
629 # update.messages.notify =
632 ## Options for package installation: excludedocs
634 ## Don't install any files which are marked as documentation.
636 ## Valid values: boolean
639 # rpm.install.excludedocs = no
642 ## Location of history log file.
644 ## The history log is described at
645 ## http://en.opensuse.org/Libzypp/Package_History
647 ## Valid values: absolute path to a file
648 ## Default value: /var/log/zypp/history
650 # history.logfile = /var/log/zypp/history
653 ## Global credentials directory path.
655 ## If a URL contains ?credentials=<filename> parameter, the credentials will
656 ## be stored and looked for in a file named <filename> in this directory.
658 ## Valid values: absolute path to a directory
659 ## Default value: /etc/zypp/credentials.d
661 # credentials.global.dir = /etc/zypp/credentials.d
664 ## Global credentials catalog file path.
666 ## This file contains a catalog of all known user credentials which were
667 ## not stored via the ?credentials=<filename> URL parameter, i.e. passed
668 ## in URL as username:password component, or entered by user in
669 ## an authentication dialog.
671 ## Valid values: absolute path to a file
672 ## Default value: /etc/zypp/credentials.cat
674 # credentials.global.file = /etc/zypp/credentials.cat