* RPM Forge is the 2nd party RPM repository
* It is an independent community-driven project to provide the infrastructure and tools to allow users, developers and packagers to meet and work together to provide and to improve RPM packages.
* This project already supports various Linux distributions and architectures and is fast expanding.
The main contributors of RPMForge are:
* Dag Wieers
* Dries Verachtert
* Matthias Saou
* Jeff Pitman
* Fernando Lopez-Lezcano
* Bert de Bruijn
In RPMforge, active participants are divided into 3 Categories. They are:
Builders: They take care of building packages for different distributions
Maintainers: They take care of packages and SPEC files
Admins: They take care of the infrastructure (such as website, mailing lists, subversions etc)
The Builder Line-up
Dag Wieers: rh7, rh9, fc1, fc2, fc3, el2, el3, el4
Dries Verachtert: au1.92, fc4
The Maintainer Line-up
* Dag Wieers: network, sysadmin, others
* Dries Verachtert: games, KDE, perl, others
* Matthias Saou: games, multimedia, others
The Admin Line-up
* Dries Verachtert
The main objectives of RPM Forge are:
* Strive for compatibility with original core and update packages from each distribution
* Will not replace core library packages from each supported distribution
* Consistency and coherency in the lay out of SPEC files
* Work towards automating as much as possible
* Work together with other similar initiatives in an open and amicable fashion
* In addition to the packages made by RPMForge Contributors, users can also add their own packages. For that, they will have to send mail to RPM Forge, add a reference to the source RPM or SPEC file. Also they must mention whether they wish to maintain this package in the future or not.
* We provide packages for a range of distributions including older RedHat distributions, Red Hat Enterprise Linux and others (eg. CentOS,Aurora) and different architectures. If the user expect to use both Fedora and Red Hat then the safest option is RPMforge.
* Since the aim of RPMForge is to merge the packages, all the packages are tagged alike. This common repotag will indicate that the packages are build from a common repository. The rf repotag is used for denoting RPMforge packages.
We have different tools built-in house and are consolidating them into one single tool.
* DAR – a build environment management tool
* pydar – our next generation build system
* Yam – a repository mirroring tool
* Mach – a chroot build environment setup tool
* Tree Tools – a collection of rpm-python tools
* XML Metadata – a new XML-base repo metadata
Advantages of RPM Forge
* We don’t replace base libraries or important core packages for repositories that are not EOL.
* Everything we do is open, users can download the SPEC files, can see the changes, also they can rebuild it.
* We communicate with developers directly and try to have things fixed upstream.
* If you experience repository conflicts, we’ll work with other repositories to fix them.
* We have a huge userbase that is being tested to provide improvements and bugfixes
* We provide packages for a variety of distributions and architectures, each of these userbases are providing us with useful feedback
Installation and Configuration
* We can use this RPM repository together with a tool that allows to automatically download an install RPM packages and resolve dependencies.
* The main tools supported are: Apt, Smart, Yum, up2date or RedCarpet.
* We make sure that the packages are tagged with a proper distribution-tag so users can easily pick the right package for their distribution.
* The packages are all signed with GPG key (public key)
RPMForge is a collaboration of Dag, Dries, and other packagers. They provide over 2600 packages for CentOS, including mplayer, xmms-mp3,and other popular media tools. It is not part of RedHat or CentOS but is designed to work with these major distributions.
Packages are supplied in RPM format and in most cases are ready to use. Beware that some packages are newer than the official CentOS version and you should not blindly install those packages. Before you replace a CentOS package you should make sure that will not break anything important. In most cases you can revert any mistakes but it is best to avoid the mess.
You should make sure that you have ProtectBase installed.
Assuming you have centos extras enabled in your current yum configuration
yum install yum-plugin-protectbase
Edit the file /etc/yum.conf and add the following line to the
Edit the file /etc/yum.repos.d/CentOS-Base.repo and add the
following line to the [base] and [update] section:
Edit /etc/yum.repos.d/CentOS-Base.repo and add the following
line to the other sections
Download the rpmforge-release package. Choose one of the two links below, depending on your architecture. If you are unsure of which one to use you can check your architecture with the command uname -i
(You can find a complete list of rpmforge-release package packages at: http://dag.wieers.com/packages/rpmforge-release/ But it is recommended that you use one of the two listed above).
Install DAG’s GPG key
rpm –import http://dag.wieers.com/rpm/packages/RPM-GPGKEY. dag.txt
Verify the package you have downloaded
rpm -K rpmforge-release-0.3.6-1.el4.rf.*.rpm
Security warning: The rpmforge-release package imports GPG keys into your RPM database. As long as you have verified the package and trust Dag then it should be safe.
Install the package:
rpm -i rpmforge-release-0.3.6-1.el4.rf.*.rpm
This will add a yum repository config file and import the appropriate GPG keys.
Test with this command:
It should output the text between these two lines (NOTE: the number of packages may change from time to time)
Loading “protectbase” plugin
76 packages excluded due to repository protections
If so then it looks like things are working so try installing something like this.
yum install mplayer
This will install mplayer.
Article Authored by Emin V
Author, Emin, is a Systems Engineer with SupportPRO. Emin specializes in Cpanel and Server Monitoring . SupportPRO offers 24X7 technical support services to Web hosting companies and service providers.