From: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: [PATCH] dev-manual: mention RM_WORK_EXCLUDE with inheriting rm_work
Date: Mon, 17 Feb 2020 08:12:35 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.2002170811030.2323392@localhost.localdomain> (raw)
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 1e6addde4..721b6c719 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -8986,6 +8986,12 @@
</literallayout>
Adding this statement deletes the work directory used for building
a recipe once the recipe is built.
+ If "rm_work" is currently selected, you can override that cleaning
+ on a per-recipe basis (typically for debugging purposes) by adding a
+ line of this form to your <filename>local.conf</filename> file:
+ <literallayout class='monospaced'>
+ RM_WORK_EXCLUDE += "busybox"
+ </literallayout>
For more information on "rm_work", see the
<ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-rm-work'><filename>rm_work</filename></ulink>
class in the Yocto Project Reference Manual.
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2020-02-17 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 13:12 rpjday [this message]
2020-02-17 13:53 ` [docs] [PATCH] dev-manual: mention RM_WORK_EXCLUDE with inheriting rm_work Quentin Schulz
2020-02-17 13:54 ` rpjday
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=alpine.LFD.2.21.2002170811030.2323392@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=docs@lists.yoctoproject.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.