How to create a GNU Hello RPM package

This is a hands-on tutorial on writing RPM files, suitable for an impatient person who wants to quickly step up to create source and binary software packages. I assume familiarity with using pre-made RPM packages, and with the FOSS software building process. More in-depth information on using and building RPM packages is available from, e.g., https://fedoraproject.org/wiki/Tools/RPM

This tutorial uses the GNU "Hello World". While 'Hello World" is a trivial program, the GNU project contains most of the usual peripheral components associated with a typical FOSS software project, such as the configuration/build/install environment, documentation, internationalization, etc., so it is a reasonable vehicle to practice building RPMs on.

I wrote this tutorial after reading Christoph Wickert's IRC class on building RPMs. Rahul Sundaram suggested using GNU "Hello World" as a test case, and it turns out that Christian Lyder Jacobsen also had this idea in 2009. Christian is not intending to update his website, so I decided to publish my version in this wiki.

Development environment

To build RPMs we need a set of development tools. This is a one-time-only setup, installed by running those commands from a system administration (root) account:

yum groupinstall development-tools
yum install rpm-build rpmdevtools

If you want to test the build procedure in the context of Fedora anonymous package build system, you need to configure your non-privileged account to be a member of the 'mock' group:

usermod -a -G mock <yourAccountName>

Those are the only commands requiring root privileges. All the remaining work should be done from your regular, non-privileged account. Modern RPM-based systems, including Fedora, are set up to build and test RPM packages purely from within a non-privileged account. The command

rpmdev-setuptree

sets up a RPM build area in your ~/rpmbuild. This directory will contain several subdirectories, for the project source code, RPM configuration files and for the resulting source and binary packages.

Building a "Hello World" RPM

We need the source code of the project we are packaging, often referred to as the 'upstream' source. We will download it from the project's website into the ~/rpmbuild/SOURCE directory. We are getting the compressed tarball archive, which happens to be a preferred distribution form for most FOSS projects.

cd ~/rpmbuild/SOURCE
wget  http://ftp.gnu.org/gnu/hello/hello-2.5.tar.gz

The RPM package is configured by .spec files. We will create a template file hello.spec in the appropriate directory:

cd ~/rpm/SPECS
rpmdev-newspec hello

Inside a .spec file

The fields in our .spec file need slight editing. Please follow the [https://fedoraproject.org/wiki/How_to_create_an_RPM_package#Spec_file_pieces_explained Fedora rules] for these fields. In our case, the file might start as follows:

Name: hello
Version: 2.5
Release: 1
Summary: The "Hello World" program
License: GPLv3
URL: http://ftp.gnu.org/gnu/hello    
Source0: http://ftp.gnu.org/gnu/hello/hello-2.5.tar.gz
%description:
The "Hello World" program, done with all bells and whistles of a proper FOSS 
project, including configuration, build, internationalization, helpfiles, etc.

%changelog
* Tue Mar 30 2010 The Coon of Ty <Ty@coon.org> 2.5-1
- Initial version of the package%changelog

The Version should mirror upstream while Release numbers our work within Fedora. The first letter of the Summary should be uppercase to avoid rpmlint complaints.

It is your responsibility to check the License status of the software, by inspecting the source files and/or their LICENSE files, and/or by talking to the authors.

The Group tag is being phased out, but it doesn't hurt to classify it in accordance to the list in /usr/share/doc/rpm-4.6.0/GROUPS.

The %changelog should document the work on preparing the RPM , and should include the version string to avoid rpmlint complains. Multi-line sections like %changelog or %description start on a line under the directive, and end with an empty line.

Lines which aren't needed (e.g. BuildRequires and Requires) can be commented out with a hash ('#') for now.

Many lines in the template don't need to be changed at all in many cases, at least for the initial attempt:

BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

%prep
%setup -q

%build
%configure
make %{?_smp_mflags}

%install
rm -rf $RPM_BUILD_ROOT
make install DESTDIR=$RPM_BUILD_ROOT

%clean
rm -rf $RPM_BUILD_ROOT

Building the package

We are ready for the first run to build source, binary and debugging packages:

rpmbuild -ba hello.spec

It will complain and list the unpackaged files, i.e. the files that would be installed in the system that weren't declared as belonging to the package. We need to declare them in the %files section. Do not hardcode names like /usr/bin/, but use macros, like %{_bindir}/hello instead. The manual pages should be declared in the %doc subsection: %doc %{_mandir}/man1/hello.1.gz.

This is an iterative process: after editing the .spec file, rerun rpmbuild.

Since our program uses translations and internationalization, we are getting a lot of undeclared i18 files. The recommended method to declare them is explained in https://fedoraproject.org/wiki/Packaging/Guidelines#Handling_Locale_Files:

• find the filenames in the %install step: %find_lang ${name}
• add the required build dependencies: BuildRequires: gettext
• use the found filenames %files -f ${name}.lang

If the program uses GNU info files, you need to do some magic:

• delete the 'dir' file in %install: rm -f $RPM_BUILD_ROOT/usr/share/info/dir
• Requires(post): info and Requires(preun): info
• add postinstall and preuninstall steps to configure info.

A complete .spec file

After few iterations, we could end up with the following initial version of a .spec file:

Name:           hello
Version:        2.5
Release:        1%{?dist}
Summary:        The "hello world" program from GNU

Group:          Applications/Text
License:        GPLv3
URL:            http://ftp.gnu.org/gnu/hello
Source0:        http://ftp.gnu.org/gnu/hello/hello-2.5.tar.gz
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildRequires: gettext
# Requires:       
Requires(post): info
Requires(preun): info

%description 
The "hello world" program from GNU, with bells and whistles


%prep
%setup -q


%build
%configure
make %{?_smp_mflags}


%install
rm -rf $RPM_BUILD_ROOT
make install DESTDIR=$RPM_BUILD_ROOT
%find_lang %{name}
rm -f $RPM_BUILD_ROOT/usr/share/info/dir

%post
/sbin/install-info %{_infodir}/%{name}.info %{_infodir}/dir || :

%preun
if [ $1 = 0 ] ; then
/sbin/install-info --delete %{_infodir}/%{name}.info %{_infodir}/dir || :
fi

%clean
rm -rf $RPM_BUILD_ROOT


%files -f %{name}.lang
%defattr(-,root,root,-)
%{_bindir}/hello
%doc %{_mandir}/man1/hello.1.gz
%doc %{_infodir}/%{name}.info.gz

%changelog
* Tue Mar 30 2010 The Coon of Ty <Ty@coon.org> 2.5-1
- Initial version of the package

With this spec file, you should be able to successfully complete the build process, and create the source and binary RPM packages.

Next you should check them for conformance with RPM design rules, by running rpmlint on the spec file and all RPMs:

rpmlint hello.spec ../SRPMS/hello* ../RPMS/*/hello*

If there are no warnings or errors, we've succeeded.

The mock builds

To check that the package build will succeed in the Fedora restricted build environment, check it with mock.

mock -r fedora-12-i386 --rebuild ../SRPMS/hello-2.5-1.fc12.src.rpm