Index of /~jlohikos/tleds/public/rpm_specs

[ICO]NameLast modifiedSizeDescription
[DIR]Parent Directory   -  
[ ]MPlayer-my.spec 07-Sep-2003 04:21 14K 
[DIR]bemusedlinuxserver/ 12-Sep-2003 17:48 -  
[DIR]ffmpeg/ 03-Sep-2003 05:08 -  
[ ]gCAD3D-0.6.2-2.spec 30-May-2003 21:11 3.7K 
[DIR]gemsvnc/ 16-Feb-2004 18:03 -  
[ ]missingdeps.spec 08-Jun-2003 21:53 2.2K 
[ ]parsemce-0.0.8-1.spec 22-May-2003 02:39 1.9K 
[ ]qt6dlls.spec 06-Jun-2003 20:53 2.0K 
[ ]rp9win32codecs.spec 26-Aug-2003 23:27 2.3K 
[ ]win32codecs.spec 26-Aug-2003 23:28 2.3K 
[ ]xmms-coverviewer-0.1..>24-May-2003 23:14 3.0K 
[ ]xvkbd.spec 16-Dec-2005 22:26 3.5K 
spec files to make a rpm packages of some software

In this directory I have rpm spec files which I have made for tarballs which themselves do not have one. By making and installing rpm packages the system stays clean and the software package is easily upgraded or erased later.

As Linux Standard Base (LSB) uses rpm packages, every Linux software tarball should have a rpm spec file included. The spec file can be in the software main directory, or any subdirectories, i.e. in foo-1.3/rpm/foo.spec

I do not officially maintain these files, just basically for my own use. The versions of the software may be obsolete and you should check first from <http://www.rpmfind.net> or from the homepage of the software if there already is rpm packages provided.

In case the original tarball needs also a patch to be buildable in RedHat OS, the patch file is mentioned in the spec file and patch file provided.

To make the rpm packages:

  1. copy the spec file to /usr/src/redhat/SPECS
  2. copy the possible patch file to /usr/src/redhat/SOURCES
  3. get the original tarball and put it to /usr/src/redhat/SOURCES (Note! the spec file probably tells you where to find the tarball. URL)
  4. Build the rpm packages with:
    'rpmbuild -ba /usr/src/redhat/SPECS/foo.spec' (or just binary package by using '-bb' instead of '-ba')
  5. Install the package i.e.
    'rpm -Uv /usr/src/redhat/RPMS/noarch/foo.noarch.rpm'

One can also build a tarball, which can be used straight with rpmbuild:

  1. untar the original tarball
  2. copy the spec file and the possible patch file to the main directory which came from the tarball.
  3. Make a new tarball which now has the spec file. (and maybe also the patch)
  4. Build the rpm packages with:
    'rpmbuild -ta /tmp/foo-1.3.tar.bz2'
    (Note! The spec file tells in "Source:"-field if it expects tar.gz or .bz2)
  5. install the binary package to the system:
    'rpm -Uv .....'

In case one wants to release the rpm packages, be sure to provide the correct 'Packager:' information in the spec file.

Also it is highly recommended to GPG sign the packages before releasing. It protects both you and the installer from abuse. See
< http://www.rpm.org/max-rpm/s1-rpm-pgp-signing-packages.html > for instructions.

Also if you do sign, your GPG public key should be found somehow. The best place would be in PGP-keyservers, i.e.
< ldap://keyserver.pgp.com >

How to get your GPG public key to the keyserver is beyond the scope of this README.

// Jouni dot Lohikoski at iki dot fi