6.4. Working with spec files

Procedure

1. Navigate to the ~/rpmbuild/SPECS directory:

   $ cd ~/rpmbuild/SPECS

2. Create a spec file for each of the three implementations of the Hello World! program:

   $ rpmdev-newspec bello
   bello.spec created; type minimal, rpm version >= 4.11.
   
   $ rpmdev-newspec cello
   cello.spec created; type minimal, rpm version >= 4.11.
   
   $ rpmdev-newspec pello
   pello.spec created; type minimal, rpm version >= 4.11.

   The ~/rpmbuild/SPECS/ directory now contains three spec files named bello.spec, cello.spec, and pello.spec.

3. Examine the created files.

   The directives in the files represent those described in About spec files. In the following sections, you will populate a particular section in the output files of rpmdev-newspec.

Procedure

1. Open the ~/rpmbuild/SPECS/<name>.spec file provided by the rpmdev-newspec utility.

2. Populate the following directives of the spec file Preamble section:

   Name

   Name was already specified as an argument to rpmdev-newspec.

   Version

   Set Version to match the upstream release version of the source code.

   Release

   Release is automatically set to 1%{?dist}, which is initially 1.

   Summary

   Enter a one-line explanation of the package.

   License

   Enter the software license associated with the source code.

   URL

   Enter the URL to the upstream software website. For consistency, utilize the %{name} RPM macro variable and use the https://example.com/%{name} format.

   Source

   Enter the URL to the upstream software source code. Link directly to the software version being packaged.

   注記

   The example URLs in this documentation include hard-coded values that could possibly change in the future. Similarly, the release version can change as well. To simplify these potential future changes, use the %{name} and %{version} macros. By using these macros, you need to update only one field in the spec file.

   BuildRequires

   Specify build-time dependencies for the package.

   Requires

   Specify run-time dependencies for the package.

   BuildArch

   Specify the software architecture.

3. Populate the following directives of the spec file Body section. You can think of these directives as section headings, because these directives can define multi-line, multi-instruction, or scripted tasks to occur.

   %description

   Enter the full description of the software.

   %prep

   Enter a command or series of commands to prepare software for building.

   %conf

   Enter a command or series of commands to configure software for building.

   %build

   Enter a command or series of commands for building software.

   %install

   Enter a command or series of commands that instruct the rpmbuild command on how to install the software into the BUILDROOT directory.

   %files

   Specify the list of files, provided by the RPM package, to be installed on your system.

   %changelog

   Enter the list of datestamped entries for each Version-Release of the package.

   Start the first line of the %changelog section with an asterisk (*) character followed by Day-of-Week Month Day Year Name Surname <email> - Version-Release.

   For the actual change entry, follow these rules:

   • Each change entry can contain multiple items, one for each change.
   • Each item starts on a new line.
   • Each item begins with a hyphen (-) character.