diff options
author | William Douglas <william.douglas@intel.com> | 2013-03-25 14:07:49 -0700 |
---|---|---|
committer | Auke Kok <auke-jan.h.kok@intel.com> | 2013-03-27 11:15:07 -0700 |
commit | f0b647223ded79068dd1d92da329d2ea95527590 (patch) | |
tree | 3a43182902cc9e7eaf007440acf3b18ebbd1361c | |
parent | 464264ac5a35b655065c5d95b8d8ffbbc7ff3bcf (diff) |
man/os-release: Add BUILD_ID field
BUILD_ID is a fairly generic field used to identify the system image
that was used to install the distribution.
-rw-r--r-- | man/os-release.xml | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/man/os-release.xml b/man/os-release.xml index 98320efe31..45babd61b9 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -298,6 +298,28 @@ <literal>BUG_REPORT_URL="https://bugzilla.redhat.com/"</literal></para></listitem> </varlistentry> + <varlistentry> + <term><varname>BUILD_ID=</varname></term> + + <listitem><para>A string uniquely + identifying the system image used as + the origin for a distribution (it is + not updated with system updates). The + field can be identical between + different VERSION_IDs as BUILD_ID is + an only a unique identifier to a + specific version. Distributions that + release each update as a new version + would only need to use VERSION_ID as + each build is already distinct based + on the VERSION_ID. This field is + optional. Example: + <literal>BUILD_ID="2013-03-20.3"</literal> + or + <literal>BUILD_ID=201303203</literal>. + + </para></listitem> + </varlistentry> </variablelist> |