Using the GTK+ Interface

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 Software+Software Manager

Searching Packages or Patterns

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:

Groups: The default view lists all packages sorted by groups such as Graphics, Programming, or Security. To lists all packages sorted by groups and subgroups, for example Productivity+Graphics+Viewers, click Detailed.
Patterns: Lists all patterns available for installation on your system.
Languages: Filter to list all packages needed to add a new system language.
Repository: 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” @System lists all packages currently installed.

Installing and Removing Packages or Patterns

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 Install. Packages available for upgrade or removal are listed under Upgrade or Remove, 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 Select All, right-click again and choose an action.

To install a pattern, choose a pattern by clicking it's name and then click Install All 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 Apply 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 Sure?. To undo changes, right-click a package and choose Undo. To abandon all changes and close the software manager, click Cancel and Quit.
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”.

Checking Software Dependencies

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 Accept, 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 Cancel and Quit the software manger. Launch it again to start again.

Figure 3.2. Conflict Management of the Package Manager