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
91 ## Whether repository urls should be probed when added
93 ## Valid values: boolean
94 ## Default value: false
96 ## If true, accessability of repositories is checked immediately (when added)
97 ## (e.g. 'zypper ar' will check immediately)
98 ## If false, accessability of repositories is checked when refreshed
99 ## (e.g. 'zypper ar' will delay the check until the next refresh)
101 # repo.add.probe = false
105 ## Amount of time in minutes that must pass before another refresh.
107 ## Valid values: Integer
110 ## If you have autorefresh enabled for a repository, it is checked for
111 ## up-to-date metadata not more often than every <repo.refresh.delay>
112 ## minutes. If an automatic request for refresh comes before <repo.refresh.delay>
113 ## minutes passed since the last check, the request is ignored.
115 ## A value of 0 means the repository will always be checked. To get the oposite
116 ## effect, disable autorefresh for your repositories.
118 ## This option has no effect for repositories with autorefresh disabled, nor for
119 ## user-requested refresh.
121 # repo.refresh.delay = 10
124 ## Maximum number of concurrent connections to use per transfer
125 ## This setting is only used if more than one is possible
126 ## Setting it to a reasonable number avoids flooding servers
128 # download.max_concurrent_connections = 2
131 ## Sets the minimum download speed (bytes per second)
132 ## until the connection is dropped
133 ## This can be useful to prevent security attacks on hosts by
134 ## providing updates at very low speeds.
138 # download.min_download_speed = 0
140 ## Maximum download speed (bytes per second)
142 # download.max_download_speed = 0
144 ## Number of tries per download which will be
145 ## done without user interaction
146 ## 0 means no limit (use with caution)
147 # download.max_silent_tries = 5
150 ## Whether to consider using a .delta.rpm when downloading a package
152 ## Valid values: boolean
153 ## Default value: true
155 ## Using a delta rpm will decrease the download size for package updates
156 ## since it does not contain all files of the package but only the binary
157 ## diff of changed ones. Recreating the rpm package on the local machine
158 ## is an expensive operation (memory,CPU). If your network connection is
159 ## not too slow, you benefit from disabling .delta.rpm.
161 # download.use_deltarpm = true
164 ## Whether to consider using a deltarpm even when rpm is local
166 ## Valid values: boolean
167 ## Default value: false
169 ## This option has no effect unless download.use_deltarpm is set true.
171 # download.use_deltarpm.always = false
174 ## Hint which media to prefer when installing packages (download vs. CD).
176 ## Valid values: download, volatile
177 ## Default value: download
179 ## Note that this just a hint. First of all the solver will choose the 'best'
180 ## package according to its repos priority, version and architecture. But if
181 ## there is a choice, we will prefer packages from the desired media.
183 ## Packages available locally are always preferred. The question is whether
184 ## you prefer packages being downloaded via FTP/HTTP/HTTPS (download), rather
185 ## than being prompted to insert a CD/DVD (volatile), in case they are available
188 ## Name | Priority | URI
189 ## openSUSE-11.1 99 dvd:///
190 ## openSUSE-11.1-Oss 99 http://download.opensuse.org/distribution/11.1/repo/oss
192 ## In the above example 2 repositories with similar content are used. Rather
193 ## than raising the priority of one of them to 'prefer' a certain media, you
194 ## should use the same priority for both and set download.media_preference
197 ## download.media_preference = download
200 ## Commit download policy to use as default.
202 ## DownloadOnly, Just download all packages to the local cache.
203 ## Do not install. Implies a dry-run.
205 ## DownloadInAdvance, First download all packages to the local cache.
206 ## Then start to install.
208 ## DownloadInHeaps, Similar to DownloadInAdvance, but try to split
209 ## the transaction into heaps, where at the end of
210 ## each heap a consistent system state is reached.
212 ## DownloadAsNeeded Alternating download and install. Packages are
213 ## cached just to avid CD/DVD hopping. This is the
214 ## traditional behaviour.
216 ## <UNSET> If a value is not set, empty or unknown, we pick
217 ## some save default.
219 ## commit.downloadMode =
222 ## Defining directory which contains vendor description files.
224 ## One file in this directory reflects a group of equivalent vendors. e.G.:
225 ## (filename is "nvidia" but could be any other name):
226 ## ------------------------- file contains begin -----------------------
229 ## vendors = nvidia,suse,opensuse
231 ## ------------------------- file contains end -----------------------
232 ## Libzypp makes an string comparision (like strncmp, case-insensitive)
233 ## whereas the beginning of the strings are compared only.
234 ## e.G. vendor "opensuse11.0" is compatible to "openSuSE".
236 ## Valid values: A directory
237 ## Default value: {configdir}/vendors.d
239 # vendordir = /etc/zypp/vendors.d
243 ## Whether required packages are installed ONLY
244 ## So recommended packages, language packages and packages which depend
245 ## on hardware (modalias) will not be regarded.
247 ## Valid values: boolean
248 ## Default value: false
250 # solver.onlyRequires = false
253 ## EXPERTS ONLY: Per default the solver will not replace packages of
254 ## different vendors, unless you explicitly ask to do so. Setting this
255 ## option to TRUE will disable this vendor check (unless the application
256 ## explicitly re-enables it). Packages will then be considered based on
257 ## repository priority and version only. This may easily damage your system.
259 ## CHANGING THE DEFAULT IS NOT RECOMMENDED.
261 ## Valid values: boolean
262 ## Default value: false
264 # solver.allowVendorChange = false
267 ## This file contains requirements/conflicts which fulfill the
268 ## needs of a running system.
269 ## For example the system would be broken if not glibc or kernel is
271 ## So the user will be informed if these packages will be deleted.
273 ## Format: Each line represents one dependency:
277 ## Default value: {configdir}/systemCheck
279 # solver.checkSystemFile = /etc/zypp/systemCheck
282 ## When committing a dist upgrade (e.g. 'zypper dup') a solver testcase
283 ## is written to /var/log/updateTestcase-<date>. It is needed in bugreports.
284 ## This optin returns the number of testcases to keep on the system. Old
285 ## cases will be deleted, as new ones are created.
287 ## Use 0 to write no testcase at all, or -1 to keep all testcases.
289 ## Valid values: Integer
292 # solver.upgradeTestcasesToKeep = 2
295 ## Packages which are parallel installable with
298 # multiversion = kernel-default,kernel-smp
301 ## Path to locks file. If not exist then is create.
302 ## In this file is saved also UI locks.
304 ## valid value: path to file or place where file can be created
305 ## default value: {configdir}/locks
307 # locksfile.path = /etc/zypp/locks
310 ## Whetever to apply locks in locks file after zypp start.
312 ## Valid values: boolean
313 ## Default value: true
315 # locksfile.apply = true
318 ## Where update items are stored
319 ## (example: scripts, messages)
321 ## Valid values: path to directory
322 ## Default value: /var/adm
324 # update.datadir = /var/adm
327 ## Where update messages are stored
329 ## Valid values: path to directory
330 ## Default value: {update.datadir}/update-messages
332 # update.messagesdir = /var/adm/update-messages
335 ## Where update scripts are stored
337 ## Valid values: path to directory
338 ## Default value: {update.datadir}/update-scripts
340 # update.scriptsdir = /var/adm/update-scripts
343 ## Command to be invoked to send update messages.
345 ## Packages may leave an update message file in {update.messagesdir}.
346 ## At the end of each commit, zypp collects those messages and may send
347 ## a notification to the user.
349 ## zypp will prepare the update messages according to the selected
350 ## content format and pipe the content to the command.
353 ## single - For each update message invoke the command and send
355 ## none - For each update message invoke the command but don't
356 ## use a pipe to send any data. You probably want to pass
357 ## the message file on the commandline using %P (see
359 ## digest - Single invocation of the command, sending the path
360 ## names of all update message. One per line.
361 ## bulk - Single invocation of the command, sending the
362 ## concatenated content of all update messages, separated
366 ## %p - package identification (name-version-release.arch)
367 ## %P - full path to the update message file
369 ## Valid values: The value is specified as "format | command".
370 ## An empty value will turn off any notification.
372 ## Examples: single | mail -s 'Update message from %p' root
373 ## none | my-send-script -f %P
375 ## Default value: single | /usr/lib/zypp/notify-message -p %p
377 # update.messages.notify = single | /usr/lib/zypp/notify-message -p %p
380 ## Options for package installation: excludedocs
382 ## Don't install any files which are marked as documentation.
384 ## Valid values: boolean
387 # rpm.install.excludedocs = no
390 ## Location of history log file.
392 ## The history log is described at
393 ## http://en.opensuse.org/Libzypp/Package_History
395 ## Valid values: absolute path to a file
396 ## Default value: /var/log/zypp/history
398 # history.logfile = /var/log/zypp/history
401 ## Global credentials directory path.
403 ## If a URL contains ?credentials=<filename> parameter, the credentials will
404 ## be stored and looked for in a file named <filename> in this directory.
406 ## Valid values: absolute path to a directory
407 ## Default value: /etc/zypp/credentials.d
409 # credentials.global.dir = /etc/zypp/credentials.d
412 ## Global credentials catalog file path.
414 ## This file contains a catalog of all known user credentials which were
415 ## not stored via the ?credentials=<filename> URL parameter, i.e. passed
416 ## in URL as username:password component, or entered by user in
417 ## an authentication dialog.
419 ## Valid values: absolute path to a file
420 ## Default value: /etc/zypp/credentials.cat
422 # credentials.global.file = /etc/zypp/credentials.cat