Creating an Eprints RPM

From EPrints Documentation
Revision as of 13:32, 20 February 2007 by Timbrody (Talk | contribs)

Jump to: navigation, search

Download EPrints Releases: http://files.eprints.org/view/type/release.html


Creating the Eprints RPM requires root, because the process involves creating the eprints user and group.

Install rpm-build (depending on your package manager):

up2date rpm-build
yum install -y rpm-build

Download the Eprints source file (eprints-x.x.x.tar.gz, version 3.0.1 and above).

Create the RPM and source RPMs (will error if there are any missing dependencies):

rpmbuild -ta eprints-x.x.x.tar.gz

The RPMs should be written to /usr/src/redhat/RPMS/ and /usr/src/redhat/SRPMS/.

Signing RPMs

See http://fedoranews.org/tchung/gpg/ for how to create a GPG key pair and signing an RPM. To avoid key warnings when using up2date or Yum all RPMs need to be signed, and the public key imported into the local system.

Building a Yum repository

Install createrepo from http://linux.duke.edu/projects/metadata/.

Create a directory structure containing RPMS and SRPMS directories:

.
./RPMS
./SRPMS

To create the repository metadata execute:

createrepo .

This should create a repodata directory.

Building an up2date repository

up2date uses an 'obsolete' repository structure and requires yum-arch (isn't in Yum version 3):

yum-arch .