Fix spelling error

[openafs-wiki.git] / devel / HowToBuildOpenAfsRpmPackages.mdwn

diff --git a/devel/HowToBuildOpenAfsRpmPackages.mdwn b/devel/HowToBuildOpenAfsRpmPackages.mdwn
index 5c0b92f..752dce2 100644 (file)
--- a/devel/HowToBuildOpenAfsRpmPackages.mdwn
+++ b/devel/HowToBuildOpenAfsRpmPackages.mdwn
@@ -2,30 +2,8 @@
 
 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`.
-
-The general process is:
-
-* Set up the RPM build directories
-* Download or extract the RPM sources
-   - Release Notes
-   - CellServDB file
-   - Source code tar file
-   - Documentation tar file
-* Extract the openafs.spec file from the openafs code tree
-   - Set the OpenAFS version and package release versions
-* Run rpmbuild -bs to create a source RPM
-* Run rpmbuild with options to create RPM package files
-
-Available resources for building RPM packages:
-
-* The OpenAFS makefile has targets to build the source RPM
-* The OpenAFS src/packaging/RedHat/makesrpm.pl script may be used to build the source RPM (This script is used by the makefile)
-* The OpenAFS-contrib [afsutil package][1] script will build RPMs in a local git repo, and has options to support building packages with `mock`.
-
+tree.  Packages may be built from the OpenAFS release tar files or from a clone
+of the OpenAFS git repository.
 
 ## How to build release packages from an OpenAFS source distribution
 
@@ -86,7 +64,7 @@ the RPM spec file in src/packaging/RedHat for `--define` options for optional
 features and packages.
 
 Note: One downside to this method is the RELNOTES and ChangeLog from the
-OpenAFS release download page are not included in the build packages.
+OpenAFS release download page are not included in the built packages.
 
 ## How to build release packages with afsutil
 
@@ -117,16 +95,17 @@ Some commonly used `afsutil package` options are:
 See `afsutil package --help` for a complete list of options.
 
 
-## Version Strings
+## A note about version strings
+
+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.
 
-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.
+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.
 
-In the following examples, set the version string the `.version` to generate a
+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.