RPM Fusion uses Plague as Build System. Long term Fedora contributors might still remember it from the Fedora Extras days; plague is also still used for EPEL. Packagers can use plague-client to request package builds and get information about the buildsystem.

Installing Plague-client

You can install plague-client from the Fedora repos using this command:

yum install plague-client

Initial Plague-client Setup

plague-client normally uses the configuration file [~/.plague-client.cfg]. RPM Fusion can't use that, as some of our contributors are participating in EPEL, which expect that the Fedora certs and informations are found in that file.

The Makefiles in RPM Fusion's CVS thus expects that you create a file .plague-client-rpmfusion.cfg in your home directory that will be used automatically when you type make build. Please use this as a template for that file; be sure to adjust your email address!

[Certs]
user-ca-cert = ~/.rpmfusion-upload-ca.cert
server-ca-cert = ~/.rpmfusion-server-ca.cert
user-cert = ~/.rpmfusion.cert

[User]
email = <FAS_registered_email>

[Server]
use_ssl = yes
address = https://buildsys.rpmfusion.org:8887
allow_uploads = False

RPMFusion Certificates

Plague uses three certificates:

• ~/.rpmfusion.cert

  This is your user certificate for RPM Fusion. You can download this cert from the Account System.
  This certificate expires once a year; you need to download it from the Accounts System anew then.

• ~/.rpmfusion-upload-ca.cert

  The certificate for the Certificate Authority used to sign the user keys.
  You can download it from the Accounts System as well.

• ~/.rpmfusion-server-ca.cert

  The certificate for the Certificate Authority used to sign the build system's server keys.
  You can download it from the Accounts System as well.

The web interface

http://buildsys.rpmfusion.org/build-status/index.psp

Building with make targets

For simple build requests, there is an alias in Makefile to request builds. This enables RPM Fusion packagers to simply change into the appropriate branch of a package (from a cvs checkout), and run:

make build

This will trigger a build request for the branch. Easy!

Note that all build requests need to be done against tagged trees ( by running make tag first).

Chained builds

Finished builds will be added to the needsign repo; this is automatically used in later builds.