Fedora yum install dekorator

Listing multiple packages for exclusion can be accomplished by quoting a space-delimited list of packages. With this setting, yum removes all packages in a package group, regardless of whether those packages are required by other packages or groups. For more information on removing packages, refer to Intelligent package group removal. Here you can provide a space-separated list of packages which yum can install , but will never update.

Refer to the yum. When one package declares in its spec file that it obsoletes another package, the latter package will be replaced by the former package when the former package is installed. Updating Packages 4. Preserving Configuration File Changes 4. Packages and Package Groups 4. Searching Packages 4. Listing Packages 4. Displaying Package Information 4. Installing Packages 4. Removing Packages 4.

Configuring Yum and Yum Repositories 4. Setting [main] Options 4. Setting [repository] Options 4. Using Yum Variables 4. Creating a Yum Repository 4. Yum Plugins 4. Enabling, Configuring and Disabling Yum Plugins 4. If you are installing packages on a multilib system, such as an AMD64 or Intel64 machine, you can specify the architecture of the package as long as it is available in an enabled repository by appending. For example, to install the sqlite2 package for i , type:.

You can use glob expressions to quickly install multiple similarly-named packages:. In addition to package names and glob expressions, you can also provide file names to yum install. Searches automatically include both installed and available packages.

The format of the results depends upon the option. If the query produces no information, there are no packages matching the criteria. Searching by Package Name and Attributes.

To search for a specific package by name, use the list function. To search for the package tsclient , use the command:. To make your queries more precise, specify packages with a name that include other attributes, such as version or hardware architecture.

To search for version 0. Valid Package Attributes Refer to Section 2. Advanced Searches. If you do not know the name of the package, use the search or provides options.

Alternatively, use wild cards with any yum search option to broaden the search criteria. The search option checks the names, descriptions, summaries and listed package maintainers of all of the available packages to find those that match. For example, to search for all packages that relate to Palm Pilots, type:. The provides function checks both the files included in the packages and the functions that the software provides.

This option requires yum to download and read much larger index files than with the search option. To search for all packages that include files called libneon , type:. To search for all packages that either provide a MTA Mail Transport Agent service, or include files with mta in their name:.

For each command, at the prompt enter the password for the root account. Use the standard wild-card characters to run any search option with a partial word or name:?

To list all packages with names that begin with tsc , type:. Understanding Matches. Searches with yum show all of the packages that match your criteria.

Packages must meet the terms of the search exactly to be considered matches, unless you use wild-cards. For example, a search query for shadowutils or shadow-util would not produce the package shadow-utils. Updating Your System with yum. Use the update option to upgrade all of your Fedora system software to the latest version with one operation.

Automatically Updating Your System. The yum package supplied with Fedora Core includes scripts to perform full system updates every day. To activate automatic daily updates, enter this command:. At the prompt, enter the password for the root account. How Daily Updates are Run There is no separate yum service that runs on your system. Configuring Access to Software Repositories. Fedora systems automatically use the Fedora Project repositories.

These include Fedora Extras, the default source of packages for software that is not included with Fedora Core. If the Fedora Project does not supply packages for a product, the manufacturer may provide or recommend a separate repository.

Members of the community also maintain repositories to provide packages for Fedora systems. Adding a Repository as a Package Source. Package providers make the definition files for their repositories available on their web sites.

Definition File Extension The names of repository definition files end with. You must have root access to add a file to the definitions directory.

To copy the definition file example. The configuration file for each repository should include a gpgkey setting. This setting specifies the location of a public key that verifies the packages provided by that repository. This public key is automatically imported the first time that you install software from the repository. If the configuration file provided does not include this setting, refer to Section 7. Manually Authorizing Package Sources. To manually add a public key to your rpm keyring, use the import feature of the rpm utility.

You may also import public keys directly from a web site. Understanding Repository Compatibility. The Fedora Extras repository provides packages which are built to the same standards as Fedora Core packages. Third-party packages should be compatible with these Fedora Project packages, unless the provider specifically states otherwise.

Always read the web site of the repository for information on package compatibility before you add it as a package source. Separate repository providers may offer different and incompatible versions of the same software. Third-party repositories may also provide alternative packages for software that is included in Fedora repositories. Alternative packages may contain versions of the software that function differently from the version in the Fedora Project packages.

Determine the benefits and potential incompatibilities before replacing Fedora Project packages with alternative versions. Incompatible Repositories If you configure your system to use incompatible repositories yum operations may fail.

Packages built for one version of Fedora are usually not compatible with other versions of Fedora. The web site of the provider should specifically state which versions of Fedora they support. Old Versions of yum and Current Repositories The data format for repository indexes changed with version 2.

This was the version supplied with Fedora Core 3. Repository providers should specify the versions of Fedora Core that they support.

Disabling or Removing Package Sources. The yum utility ignores any definition file with this setting. Installing Software from an Isolated Package.

Use repositories and the standard yum commands to locate and install new software, unless the software package is not available from any repository. In these cases, use the localinstall function to install the software from the package file. Public Key is Required Ensure that the public key for the package source has been imported before you install a package without a repository. Refer to Section 7. Enter this command to install the package tsclient Previously Installed Software is Updated If the package provides a later version of software that is already installed on your system, yum updates the installed software.

If the package requires software that is not installed on your system, yum attempts to meet the dependencies with packages from the configured repositories. You may need to manually download and install additional packages in order to satisfy all of the dependencies.

Maintaining Manually Installed Software If you install software that is not provided by a repository, yum update cannot automatically upgrade it as new versions become available. To ensure that you have the latest packages, subscribe to e-mail or RSS services that notify you when new versions are released. Customizing yum. To change the behavior of yum , you may either edit the configuration files, or install plugins.