To be able to use this plugin, you must enable plugins in your /etc/yum.conf file, see Yum Plugins for details. This plugin is particularly useful for anyone who uses one or more third-party repositories, as these repositories may update system files, which can potentially compromise the stability of your CentOS installation. The priorities are also in effect when a new package is installed - if a package is in more than one repository, it will be installed from the repository with the highest priority. Packages from repositories with a lower priority will never be used to upgrade packages that were installed from a repository with a higher priority. The priorities plugin can be used to enforce ordered protection of repositories, by associating priorities to repositories. It functions in a substantially similar ways in these three CentOS major releases CentOS-6 has reverted to yum-plugin-priorities. It is named yum-priorities on CentOS-5 but was named yum-plugin-priorities on CentOS-4. Note: This plugin has carried at least two differing names over time. This can let you choose which packages a less important repo will supersede those of a more important one. It can be used in conjunction with the 'exclude' and/or 'includepkg' options, as well as the 'enabled=0' option to disable a repo by default. For this purpose, a repo is considered clean when its disk usage doesn't exceed 64KB (that is to account for directory entries and tiny metadata files such as "productid" that are never cleaned).Many people find the priorities plugin to be a useful tool if properly configured, and used with an understanding of the functionality and a recognition of the limitations and potential issues. As a convenience, if this command does not result in a completely empty cache due to the restrictions outlined at the beginning of this section, a message will be printed, saying how much disk space can be reclaimed by cleaning the remaining repos manually. Tell any enabled plugins to eliminate their cached data.ĭoes all of the above. Using this option will force yum to download the sqlite metadata the next time it is run, or recreate the sqlite metadata if using an older repo.Įliminate any cached data from the local rpmdb. Using this option will force yum to download all the metadata the next time it is run.Įliminate the sqlite cache used for faster access to metadata. Note that packages are not automatically deleted after they are downloaded.Įliminate all of the header files, which old versions of yum used for dependency resolution.Įliminate all of the files which yum uses to determine the remote availability of packages. However if the cache is still valid, nothing significant was deleted.Įliminate any cached packages from the system. This means yum will revalidate the cache for each repo. Taken from "man yum" ?clean CLEAN OPTIONSĮliminate the local data saying when the metadata and mirrorlists were downloaded for each repo.
0 kommentar(er)
