Only packages signed with the relevant CentOS GPG key are products of the CentOS project.

For instance, the CentOS 'testing' archive is one that does NOT seek to expressly provide an update path. Most of the sources listed in the 'Repositories' wiki page have such resources and features, but some do not. Most people using repositories expect support (mailing list, fora, bug tracker, IRC channel), and an archive which issues security and feature updates on the packages it provides. Before deciding to rebuild a SRPM, you should probably look for the desired package in one of the available Repositories to see if they already contain the package you seek. You will have to maintain it and rebuild it every time that security updates are available. After building packages you may want to consider setting up a local repo to simplify package management using yum or GUI tools.įirst consider the burden that rebuilding a SRPM will be for you.

There are considerable benefits to using a package management system to manage dependencies versus source installs. Even if the software is not available in CentOS, you should always try to get or build a RPM for the software, since the advantages of using a package management system will compensate for the work you will have building the package. One of the reasons why you may want to do this is to install a software package that is not available in CentOS repositories. This document will guide you on how to rebuild a Source RPM (SRPM) package on your CentOS distribution.

Centos install rpm