diff options
| author |   Sebastian Pipping <sebastian@pipping.org> | 2012-07-09 18:24:18 +0200 |
|---|---|---|
| committer | Sebastian Pipping <sebastian@pipping.org> | 2012-07-09 18:24:18 +0200 |
| commit | 82d78d5ab9b4c0275ce36b098186b0c24dc77797 (patch) | |
| tree | ae03a4d0aa1f807ac92507264684cea39205512d | |
| parent | Man page: Make use of code block syntax (diff) | |
| download | catalyst-82d78d5ab9b4c0275ce36b098186b0c24dc77797.tar.gz catalyst-82d78d5ab9b4c0275ce36b098186b0c24dc77797.tar.bz2 catalyst-82d78d5ab9b4c0275ce36b098186b0c24dc77797.zip | |
Man page: Adjust language
| -rw-r--r-- | doc/catalyst-spec.5.txt | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/catalyst-spec.5.txt b/doc/catalyst-spec.5.txt index 2851c174..b42983f7 100644 --- a/doc/catalyst-spec.5.txt +++ b/doc/catalyst-spec.5.txt @@ -45,12 +45,12 @@ The subarch can be any of the supported catalyst subarches (example: supported subarches. *version_stamp*:: -The version stamp is an identifier for the build. It can be anything -you wish it to be, but it is usually a date (example: `2006.1`). +The version stamp is an identifier for the build. It can be anything, +but something date-like is recommended (example: `2006.1`). *target*:: -The target specifies what target we want catalyst to do (example: -`stage3`). Possible targets are: +The target specifies what target we want catalyst to build (example: +`stage3`). Supported targets are: include::targets.generated.txt[tabsize=4] @@ -69,7 +69,7 @@ This specifies which snapshot to use for building this target (example: `2006.1`). *source_subpath*:: -This specifies where the seed stage comes from for this target +This specifies where the seed stage for this target comes from (example: `default/stage3-x86-2006.1`). The path is relative to `$storedir/builds`. The `rel_type` is also used as a path prefix for the seed. @@ -94,7 +94,7 @@ like to use when building this target (example: `/usr/local/portage`). This allows the optional directory containing the output packages for catalyst (example: `/tmp/packages`). Mainly used as a way for different spec files to access the same cache directory. Default -behavior is for this location to be autogenerated under `$storedir` +behavior for this location is to be autogenerated under `$storedir` based on the spec file. *kerncache_path*:: |