ref-manual: New glossary entries

I added glossary definitions for BUGTRACKER and
CLASSOVERRIDE.

(From yocto-docs rev: 11517aa35b0ce694749f3ec55f452976f26f8166)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-11-15 10:59:39 -08:00 committed by Richard Purdie
parent fcae7ef9c5
commit 4d3730597d
1 changed files with 36 additions and 0 deletions

View File

@ -826,6 +826,18 @@
</glossdef>
</glossentry>
<glossentry id='var-BUGTRACKER'><glossterm>BUGTRACKER</glossterm>
<glossdef>
<para>
Specifies a URL for an upstream bug tracking website for
a recipe.
The OpenEmbedded build system does not use this variable.
Rather, the variable is a useful pointer in case a bug
in the software being built needs to be manually reported.
</para>
</glossdef>
</glossentry>
<glossentry id='var-BUILDDIR'><glossterm>BUILDDIR</glossterm>
<glossdef>
<para>
@ -877,6 +889,30 @@
</glossdef>
</glossentry>
<glossentry id='var-CLASSOVERRIDE'><glossterm>CLASSOVERRIDE</glossterm>
<glossdef>
<para>
An internal variable specifying the special class override
that should currently apply (e.g. "class-target",
"class-native", and so forth).
The classes that use this variable set it to
appropriate values.
</para>
<para>
You do not normally directly interact with this variable.
The value for the <filename>CLASSOVERRIDE</filename>
variable goes into
<link linkend='var-OVERRIDES'><filename>OVERRIDES</filename></link>
and then can be used as an override.
Here is an example:
<literallayout class='monospaced'>
DEPENDS_append_class-native = " python-native"
</literallayout>
</para>
</glossdef>
</glossentry>
<glossentry id='var-COMBINED_FEATURES'><glossterm>COMBINED_FEATURES</glossterm>
<glossdef>
<para>A set of features common between