ref-manual: explain how to un-blacklist a recipe
PATCH 1/1 ref-manual: explain how to un-blacklist a recipe
Add to explanation of PNBLACKLIST variable how to un-blacklist a recipe, and the conditions under which that's allowed.
Signed-off-by Robert P. J. Day <[email protected]>
---
documentation/ref-manual/ref-variables.xml +17 -1
@@ -10771,11 +10771,27 @@ <filename>PNBLACKLIST</filename> variable in your <filename>local.conf</filename> file. Here is an example that prevents - <filename>myrecipe</filename> from being built: + <filename>myrecipe</filename> from being built, + along with the reason for its blacklisting: <literallayout class='monospaced'> PNBLACKLIST[myrecipe] = "Not supported by our organization." </literallayout> </para> + + <para> + If the blacklisting was done in the recipe file itself, + you can un-blacklist that recipe by setting its blacklist + reason to the empty string in your + <filename>local.conf</filename> file, as in: + <literallayout class='monospaced'> + PNBLACKLIST[myrecipe] = "" + </literallayout> + but only if the blacklisting was done with a weak + assignment in the recipe file thusly: + <literallayout class='monospaced'> + PNBLACKLIST[myrecipe] ?= "Not supported by our organization." + </literallayout> + </para> </glossdef> </glossentry>
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================