Contents
Abstract
In YaST's software management tool search for software components you want to add or remove. YaST resolves all dependencies for you. Add additional software repositories to your setup to install packages not shipped with the installation media and let YaST manage them. Keep your system up-to-date by managing software updates with openSUSE Updater.
Change the software collection of your system using YaST. This YaST module is available in three toolkit flavors: Qt, GTK+, and ncurses; Qt and GTK+ flavors are described here, see Chapter 10, YaST in Text Mode for details on the ncurses YaST.
![]() | Changing the toolkit flavor |
---|---|
By default, YaST is started with the toolkit matching your desktop
(GTK+ under GNOME, Qt under KDE). Change the variable
You may also use the options |
A local or remote directory containing packages, plus additional information about these packages (package meta-data).
A short name for a repository used by various zypper commands. The alias can be chosen by the user when adding a repository and must be unique.
Represents a whole product, for example openSUSE.
A pattern is an installable list of packages needed for a special
purpose. Examples are Base System
, providing
the openSUSE basic system, or GNOME Base
System
, containing all packages needed to run the GNOME
Desktop environment.
A package is a compressed file in rpm format that contains the files for a particular program.
A patch consists of one or more packages—either full packages or patchrpm or deltarpm packages— and may also introduce dependencies to packages that are not installed yet.
An generic term for product, pattern, package or patch. The most commonly used type of resolvable is a package or a patch.
A patchrpm consists only of files that have been updated since it was first released for openSUSE 11.3. Its download size is usually considerably smaller than the size of a package.
A deltarpm consists only of the binary diff between two defined versions of a package, and therefore has the smallest download size. Before being installed, the rpm package must be rebuilt on the local machine.
The YaST Qt interface is started by default when using the desktops KDE, icewm, and others. It is also used when invoking YaST from a remote terminal. Start the software manager from the YaST Control Center by
+![]() |
The YaST software manager can install packages or patterns from all currently-enabled repositories. It offers different views and filters to make it easier to find the software you are searching for. Change the view by clicking
and selecting a view listed below. The selected view opens in a new tab.The package search interface is the default view of the software manager. Enter a search term and press Enter. Refine your search by specifying where to and by changing the .
Lists all patterns available for installation on your system.
Lists all packages sorted by groups such as
, , or .Lists all packages sorted by groups and subgroups, for example
+ + .Filter to list packages by repository. In order to select more than one repository, hold the Ctrl key while clicking on repository names. The “pseudo repository” lists all packages currently installed.
Filter to list all packages needed to add a new system language.
![]() | Finding Packages Not Belonging to an Active Repository |
---|---|
To list all packages that do not belong to an active repository, choose + + and then choose + . This is for example useful if you have deleted a repository and would like to make sure no packages from that repository remain installed. |
Search for packages as described in Section 3.2.1, “Searching Packages or Patterns”.
The packages found are listed in the right pane. Select a package for installation or removal by right-clicking it and choosing Shift+F1 for help.
or . If the relevant option is not available, check the package status indicated by the symbol in front of the package name—hit![]() | Applying an Action to All Packages Listed |
---|---|
To apply an action to all packages listed in the right pane, choose an action from + . |
To install a pattern, right-click the pattern name and choose
. It is not possible to delete patterns.If your choice results in a dependency conflict that cannot be automatically solved, you need to manually solve this conflict as described in Section 3.2.3, “Checking Software Dependencies”.
In order to select more packages, repeat the steps mentioned above. Once you are finished click
to start the installation.![]() | Reviewing the Package Selection |
---|---|
YaST maintains a list with all actions that will be carried out when starting the installation. To review this list, choose Shift+F1 for details on the status flags. + . By default, all packages that will change status, are listed. Use the check boxes under to filter these list. HitIn order to revert the status for a package, right-click it and select if the package was scheduled to be deleted or updated, or if it was scheduled for installation. To abandon all changes and close the software manager, click and |
Certain packages are dependent on other packages, such as shared libraries. YaST automatically resolves these dependencies. On the other hand, some packages cannot co-exist with others on the system. In this cases, a list of packages that have automatically been chosen for installation, update or removal is presented. Accept them by clicking continue.
Once all selected packages are installed or removed, the YaST package manager automatically terminates.
![]() | Installing Sources |
---|---|
Installing source packages with the YaST software manager is not possible at the moment. Use the command line tool zypper for this purpose. For more information, see Section 7.1.2.1, “Installing Source Packages”. |
![]() | Updating packages |
---|---|
To update all packages from a certain repository, choose the repository as described in Section 3.2.1, “Searching Packages or Patterns” and then choose + + . To update all installed packages, choose + +Choosing “update” all selected packages to the version from the repository with the highest priority, even if this means actually downgrading the package. This option is for example useful to ensure that the package selection will originate from a certain repository. instead of will |
Most packages are dependent on other packages. If a package, for example, uses a shared library, it will be dependent on the package providing this library. On the other hand some packages cannot coexist with each other (you can for example only install one mail transfer agents, sendmail or postfix), causing a conflict. When installing or removing software, the software manager makes sure no dependencies or conflicts remain unresolved, hence ensuring system integrity.
In case there is just one simple solution to resolve a dependency or a conflict, it is resolved automatically. Multiple solutions always cause a conflict which needs to be resolved automatically. If solving a conflict involves a vendor or architecture change, it also needs to be solve manually. Once you start the installation by clicking
, you will get an overview of all actions triggered by the automatic resolver which you need to confirm.By default, dependencies are automatically checked. A check is performed every time you change a package status (for example by marking a package for installation or removal). This is generally useful, but can become cumbersome when manually resolving a dependency conflict. To disable it, uncheck
+ . Manually perform a dependency check with + . A consistency check is always performed when you confirm your selection with .To review a package's dependencies, right-click it and choose
. A map showing the dependencies opens. Packages that are already installed are displayed in a green frame.![]() | Manually Solving Package Conflicts |
---|---|
Unless you are very experienced, follow the suggestions YaST makes when handling package conflicts, otherwise you may not be able to resolve them. Keep in mind that every change you make, potentially triggers other conflicts, so you can easily end up with a steadily increasing number of conflicts. In case this happens, the software manger, all your changes and start again. |
The YaST GTK+ interface is started by default when using the desktops GNOME and XFCE. Start the software manager from the YaST Control Center by
+![]() |
The easiest way to find a package is to use the search field in the upper right corner of the software manager. Enter a search term and press Enter. By default it will search package names and summaries. Press the search item to change this filter and search the file lists, for example. The software manager also offers different views and filters for displaying package lists. These are available from the pull-down menu in the upper left corner:
The default view lists all packages sorted by groups such as
, , or . To lists all packages sorted by groups and subgroups, for example + + , clickLists all patterns available for installation on your system.
Filter to list all packages needed to add a new system language.
Filter to list packages by repository. In order to select more than one repository, hold the Ctrl key while clicking on repository names. The “pseudo repository” lists all packages currently installed.
Search for packages as described in Section 3.3.1, “Searching Packages or Patterns”.
The packages found are listed in the right pane. Packages that can be selected for installation are listed under the tab
. Packages available for upgrade or removal are listed under or , respectively. Click on the checkbox in front of the package to mark it for installation, removal, or upgrade.![]() | Applying an Action to All Packages Listed |
---|---|
To apply an action to all packages listed in the right pane, right-click a package, choose , right-click again and choose an action. |
To install a pattern, choose a pattern by clicking it's name and then click
in the bottom right corner.If your choice results in a dependency conflict that cannot be automatically resolved, you need to manually solve this conflict as described in Section 3.2.3, “Checking Software Dependencies”.
In order to select more packages, repeat the steps mentioned above. Once you are finished, click
to review all actions and start the installation.YaST maintains a list with all actions that will be carried out when starting the installation. All packages that will change status are listed. Accept the changes and start the installation by clicking
. To undo changes, right-click a package and choose . To abandon all changes and close the software manager, click and .Once all selected packages are installed or removed, the YaST package manager automatically terminates.
![]() | Installing Sources |
---|---|
Installing source packages with the YaST software manager is not possible at the moment. Use the command line tool zypper for this purpose. For more information, see Section 7.1.2.1, “Installing Source Packages”. |
Most packages are dependent on other packages. If a package, for example, uses a shared library, it will be dependent on the package providing this library. On the other hand, some packages cannot coexist with each other (you can for example only install one mail transfer agents, sendmail or postfix), causing a conflict. When installing or removing software, the software manager makes sure no dependencies or conflicts remain unresolved, hence ensuring system integrity.
In case there is just one simple solution to resolve a dependency or a conflict, it is resolved automatically. Multiple solutions always cause a conflict which needs to be resolved automatically. If solving a conflict involves a vendor or architecture change, it also needs to be solve manually. Once you start the installation by clicking
, you will get an overview of all actions triggered by the automatic resolver which you need to confirm.![]() | Manually Solving Package Conflicts |
---|---|
Unless you are very experienced, follow the suggestions YaST makes when handling package conflicts, otherwise you may not be able to resolve them. Keep in mind that every change you make, potentially triggers other conflicts, so you can easily end up with a steadily increasing number of conflicts. In case this happens, click and the software manger. Launch it again to start again. |
Add additional software repositories to your system to install third-party software. By default, the product repositories such as openSUSE-DVD 11.3 and a matching update repository are automatically configured during the installation. Depending on the initially selected product, a separate language add-on repository with translations, dictionaries, etc. might also be configured.
Here also manage subscriptions to so-called
. A Service in this context is a (RIS) that can offer one or more software repositories. Such a Service can be changed dynamically by its administrator or vendor.![]() | Trusting External Software Sources |
---|---|
Before adding external software repositories to your list of repositories, make sure this repository can be trusted. openSUSE is not responsible for any potential problems arising from software installed from third-party software repositories. |
To add product repositories either click
directly in the pane of the YaST control center, or + in the module. Proceed as follows:Click
.Select the repository type. Normally you will want to stick with the default
. For add-on CDs or DVDs choose the relevant option. Each repository provides files describing content of the repository. Check to download these files now. If the option is unchecked, YaST will automatically download the files when it needs them later. Click .Either provide the necessary data or insert the medium. Confirm with Section 3.2, “Using the Qt Interface” resp. Section 3.3, “Using the GTK+ Interface”.
. It will take some time until YaST has downloaded and parsed the metadata of the repository. Once done you can install software from this repository as described inIf you want to add a repository of the openSUSE® Build Service, such as the Mozilla repository (containing packages with the most recent versions of Firefox and Thunderbird), use the
configuration dialog of YaST:Start the YaST module
.Click
.Choose
and proceed with .From the preconfigured list of repositories choose the ones you would like to add by ticking the respective check boxes. The Mozilla repository, for example, is listed as
.Confirm with
.Accept to
the GnuPG key. You need to import a key for each repository you have chosen.The new software repositories are now listed in the
overview. Click to leave the software repositories configuration.The
overview of the lets you change the following properties of the repositories:The repository status can either be
or disabled. You can only install packages from repositories that are enabled. Disable a repository to turn it off temporarily. In order to completely remove a repository, it rather than disable it.![]() | |
Double-clicking on a repository name toggles its status. |
When refreshing a repository, its content description (package names, versions, etc.) is downloaded to a local cache that is used by YaST. It is sufficient to do this once for static repositories such as CDs or DVDs, whereas repositories whose content changes often should be refreshed frequently. The easiest way to keep a repositories cache up-to-date is to
it. You can also do a manual refresh by clicking on the button.
Packages from remote repositories are downloaded before being
installed. By default, they are deleted upon a successful
installation. Activating /etc/zypp/zypp.conf
, by default it
is /var/cache/zypp/packages
.
The 0
and 200
, where
0
is the highest priority. If a package is
available in more than one repository, then the repository with the
highest priority takes precedence. This is useful if you want to give
a local repository (for example, a DVD) a higher priority to avoid
downloading packages unnecessarily from the Internet, although they
have the same or a higher version number.
![]() | Priority vs. Version |
---|---|
The repository with the highest priority takes precedence in any case, even when this means to not install the package with the highest version number. Therefore make sure that the update repository always has the highest priority (20 by default), otherwise you might install an outdated version that will not get updated until the next online update. On the other hand, if you add repositories providing new versions for programs shipped with openSUSE (for example a repository with the latest KDE or GNOME version), make sure it has got a higher priority than the standard repositories, otherwise packages from these repositories will not be installed by default. |
To change a repository name or it's URL, select it from the list with a single click and then click
.To ensure their integrity, software repositories can be signed with the GPG Key of the repository maintainer. Whenever you add a new repository, YaST offers the ability to import its key. Verify it as any other GPG key and make sure that it does not change. If you detect a key change, something could be wrong with the repository and you should disable it as an installation source until you know the cause of the key change.
To manage all imported keys, click
in the module. Select an entry with the mouse to see the key properties. new keys, or existing ones.