[oe-commits] [bitbake] 03/03: bitbake-user-manual: Added information for using single quotes

[git at git.openembedded.org]

rpurdie pushed a commit to branch master
in repository bitbake.

commit 01e331cd0d612013badfb07df91151907f74903d
Author: Scott Rifenbark <srifenbark at gmail.com>
AuthorDate: Wed Sep 21 14:03:10 2016 -0700

    bitbake-user-manual: Added information for using single quotes
    
    Fixes [YOCTO #10293]
    
    In the section about setting variables, I added a paragraph that
    explains the use of single quotes when setting a variable.  The
    case covers when you must have the double quote charater as part
    of your variable's value.
    
    Signed-off-by: Scott Rifenbark <srifenbark at gmail.com>
    Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
 doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index dcb1f1e..ada4e22 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -44,6 +44,21 @@
      VARIABLE = " "
                 </literallayout>
             </para>
+
+            <para>
+                You can use single quotes instead of double quotes
+                when setting a variable's value.
+                Doing so allows you to use values that contain the double
+                character:
+                <literallayout class='monospaced'>
+     VARIABLE = 'I have a " in my value'
+                </literallayout>
+                <note>
+                    Unlike in Bourne shells, single quotes work identically
+                    to double quotes in all other ways.
+                    They do not suppress variable expansions.
+                </note>
+            </para>
         </section>
 
         <section id='variable-expansion'>

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.