Brontekst bekijken

{{intro-frame|'''Zypper''' is een gemakelijk te gebruiken commandoregel pakketbeheer programma, die gebruik maakt van de software pakketbeheer biblliotheek genaamd [[Libzypp|libzypp]]. Zypper kan installatiebronnen bewerken, zoeken naar pakketten, pakketten installeren, verwijderen of opwaarderen en meer. Het kan gebruikt worden als een zelfstandige applicatie of in scripts. Voor gebruiksinstructies kijk op '''[[Zypper/Usage]]'''. Voor informatie over ontwikkeling kijk op '''[[Zypper/Development]]'''.}}
{{Translate}}

__TOC__


==General Information==

[[Zypper/Features|Features]] | [[Zypper/Usage|Usage]] | [[Zypper/Troubleshooting|Troubleshooting]] |
[[Zypper/Versions|Versions]] | [[Zypper/History|History]] | [[Zypper/Packages|Getting Zypper]] | [[Zypper/People|People]]

<div style="background-color:#e0f2ce">

==Ondersteunde Software Installatiebronnen==
</div>
Zypper kan met verschillende software installatiebronnen overweg,als ze ondersteund worden door [[Libzypp|Libzypp]]. Op dit moment worden de volgende installatiebronnen ondersteund:
Zypper can work with various package repositories, supported by [[Libzypp]]
These currently are:
* [[Standards/YaST2_Repository_Metadata|YaST2]] repositories (used also on the installation CDs, also known as ''susetags'')
* [[Standards/Rpm_Metadata|XML RPM Metadata]] repositories (also known as ''YUM'' or ''rpm-md'')
* Plain directory containing one or more RPM packages (''Plaindir'')

'''Note''' that zypper does not use the zmd (ZENworks Management Daemon) database. 


<div style="background-color:#e0f2ce">

==Supported Resource Objects==
</div>
Zypper works with different resource objects, called resolvables. Currently, the following resolvable types are supported:

{|
|-
| '''package''' 
| this is the most commonly used type which represents a common RPM package
|-
| '''patch''' 
| update of the packages, which can include common or patch RPM packages, special scripts and messages
|-
| '''pattern'''  
| a group of packages 
|-
| '''language'''  
| a group of packages with language support
|-
| '''product''' 
| a group of packages, which are necessary to install a product
|}


<div style="background-color:#e0f2ce">
==Packages==
</div>

Zypper is in [[Development_Version|openSUSE 10.2 since Beta1]]. For 10.1, there is [http://artax.karlin.mff.cuni.cz/~martin/misc/zypper/ zypper built for libzypp-1.x.x] or [http://ftp.gwdg.de/pub/linux/misc/suser-guru/zypp/ zypper along with newest libzypp].


<div style="background-color:#e0f2ce">
==Troubleshooting==
</div>
===Verbose Output===
There is a global <tt>--verbose</tt> option that can be used multiple times to increase verbosity (2 levels currently) of zypper's output to find out what is going on. For example, use <tt>zypper -vv up</tt>.

===Log===
When filing [[bugs]], please use component [[libzypp]] and attach the log and zypper output. If you can easily reproduce the bug, there is no need to attach the whole log from previous runs. When reproducing the bug, prepend <tt>ZYPP_LOGFILE=logfile_name</tt> to the zypper command you are about to execute, and attach the file you specified:

<pre>
$ ZYPP_LOGFILE=zypper.log zypper -vv install MozillaFirefox
</pre>

Since version 0.8.0, the zypper log is <tt>/var/log/zypper.log</tt>.

===Solver Test Case===

Since version 0.8.7, zypper is able to generate a solver test case to help debugging problems related to package dependencies and libzypp's dependency resolver. To generate a test case, use the '''--debug-solver''' command option with install, remove, and update commands:

<pre>
$ zypper install --debug-solver MozillaFirefox
</pre>

The test case files will be written into <tt>/var/log/zypper.solverTestCase</tt> directory. You can pack and compress and attach them to a bug report then.

===Discussing usage and bugs===
You can discuss the general usage and troubleshooting of zypper on the [[Communicate/Mailinglists#User.2FSupport_Lists|opensuse mailing list]].   To reach zypper developers directly, you can use the [[ZYPP_Mailing_Lists|zypp-devel mailing list]].


===Ignore still running zypper===

During development of applications, it can be useful to ignore a lock for zypper (don't try this on production machines!):
<pre>
$ export ZYPP_READONLY_HACK=1
$ zypper ...
</pre>

<div style="background-color:#e0f2ce">

==Adding Build Service Repositories==
</div>

See the [[Build Service]] [[Build_Service/User| user page]].



[[Category:Package Management]]
[[Category:Installation]]
[[de:Zypper]]
[[fr:Zypper]]
[[ru:Zypper]]