From 0aaea60ea9f5940ba43f0f3df09d3f928876b9c3 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Tue, 26 Nov 2013 08:13:22 -0800
Subject: [PATCH] ref-manual: Added blacklist class description.

(From yocto-docs rev: 65b0b7f0675428566d72601fecaa7ef7c71311c6)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/ref-manual/ref-classes.xml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index 3fa50155a8..c1c3baa392 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -234,6 +234,28 @@
     </para>
 </section>
 
+<section id='ref-classes-blacklist.bbclass'>
+    <title><filename>blacklist.bbclass</filename></title>
+
+    <para>
+        The blacklist (<filename>blacklist</filename>) class prevents
+        the OpenEmbedded build system from building specific recipes
+        (blacklists them).
+        To use this class, inherit the class globally and set
+        <filename>PNBLACKLIST</filename> for each recipe you wish to blacklist.
+        Specify the <link linkend='var-PN'><filename>PN</filename></link>
+        value as a variable flag (varflag) and provide a reason, which is
+        reported, if the package is requested to be built as the value.
+        For example, if you want to blacklist a recipe called "exoticware",
+        you add the following to your <filename>local.conf</filename>
+        or distribution configuration:
+        <literallayout class='monospaced'>
+     INHERIT += "blacklist"
+     PNBLACKLIST[exoticware] = "Not supported by our organization."
+        </literallayout>
+    </para>
+</section>
+
 <section id='ref-classes-debian'>
     <title>Debian Renaming - <filename>debian.bbclass</filename></title>