From: leonardo.sandoval.gonzalez@linux.intel.com
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 2/3] bitbake-user-manual-metadata: include a space on a append example
Date: Mon, 2 Oct 2017 08:38:48 -0700 [thread overview]
Message-ID: <20171002153849.24922-2-leonardo.sandoval.gonzalez@linux.intel.com> (raw)
In-Reply-To: <20171002153849.24922-1-leonardo.sandoval.gonzalez@linux.intel.com>
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
By definition, the override operator "_append" does not include a space,
so include it.
Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
---
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index b37da10a..0cfa53d0 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -669,7 +669,7 @@
<literallayout class='monospaced'>
DEPENDS = "glibc ncurses"
OVERRIDES = "machine:local"
- DEPENDS_append_machine = "libmad"
+ DEPENDS_append_machine = " libmad"
</literallayout>
In this example, <filename>DEPENDS</filename> becomes
"glibc ncurses libmad".
--
2.12.3
next prev parent reply other threads:[~2017-10-02 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 15:38 [PATCH 1/3] bitbake-user-manual/bitbake-user-manual: remove YP as build system leonardo.sandoval.gonzalez
2017-10-02 15:38 ` leonardo.sandoval.gonzalez [this message]
2017-10-02 15:38 ` [PATCH 3/3] README: new readme file including main aspects of the project leonardo.sandoval.gonzalez
2017-10-02 16:02 ` akuster
2017-10-02 16:06 ` Alexander Kanavin
2017-10-02 17:04 ` akuster
2017-10-02 17:05 ` Leonardo Sandoval
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171002153849.24922-2-leonardo.sandoval.gonzalez@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.