Providing feedback
We have a few mailinglists where you can provide feedback.
Sending improvements and bugfixes
If you have found a problem with one of our packages, or you have some improvements, follow these steps:
Check if you are using the latest RPM
Verified the SPEC file in subversion
Please create a working patch against the latest SPEC file
Send your updates to the suggest mailinglist at: suggest@lists.rpmforge.net . You can subscribe to this list at http://lists.rpmforge.net/mailman/listinfo/suggest
Contributing new packages
If you are interested in a new package that not already exists in RPMforge, please follow these steps:
Check if it is not already in RPMforge
- Create a SPEC file that builds on your system
Contribute the SPEC file by sending it to the suggest mailinglist at: suggest@lists.rpmforge.net . You can subscribe to this list at http://lists.rpmforge.net/mailman/listinfo/suggest
Missing package for your distribution
It happens that some packages or version does not build for the distribution you were looking for. Many reasons are possible:
- The package has missing requirements
- The package simply fails to compile
- The package was not build, but builds fine
We provide buildlogs for each of these packages, please investigate first the buildlogs and try building it yourself, so that the feedback we receive may actually include a fix, or at least a proper description of the problem and the attempts you made.
In some cases it is simply impossible to create a package for a certain distribution because the distribution is too old or requires replacement of core packages to make it work.
Providing feedback
If you just want to request a new package, or you found an error that is easy to fix. Please do consider making a package yourself (or at least finding an existing one via Google) or consider making a patch instead of sending this error. It helps a lot if other people already did the required investigations before using our packagers free time. Only this way the packaging really scales.