This pages describes how to build OpenAFS client and server packages for RHEL
and CentOS using the contributed RPM spec file available in the OpenAFS source
-tree. Packages may be build from the OpenAFS release tar files or from a clone
-of the OpenAFS git repository. It is recommended to use Fedora `mock` to build
-packages, especially if you are building packages for multiple kernel versions.
-This page describes how to build packages with and without `mock`.
+tree. Packages may be built from the OpenAFS release tar files or from a clone
+of the OpenAFS git repository.
The general process is:
See `afsutil package --help` for a complete list of options.
-## Version Strings
+## A note about version strings
-A note about version strings. RPM packages require a valid version string and
-package release number. If you are building packages for version which is not
-a release (or pre-release), for example perhaps you want to make changes and
-build packages for testing, perhaps you wish to deploy packages with custom
-changes or fixes, you will need to set a customized version string in the spec
-file.
+RPM packages require a valid version string and package release number. If you
+are building packages for a non-release version (or not a pre-release), you
+will need to set a customized version string in the spec file.
-In the following examples, set the version string the `.version` to generate a
+For example, perhaps you want to make changes and build packages for testing,
+or perhaps you wish to deploy packages with custom changes or fixes. In these
+cases you will need to provide a customized version string.
+
+Specify your customer version string in the `.version` file to generate a
`openafs.spec` file with your desired version. If you are using the `afsutil
package` contributed script, use the `--version` option to specify your custom
version.