From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel: Clean DEPLOYDIR before do_deploy runs
Date: Mon, 25 Jan 2016 10:47:17 -0500 [thread overview]
Message-ID: <56A64385.1020804@windriver.com> (raw)
In-Reply-To: <1453734454.25948.13.camel@linuxfoundation.org>
On 2016-01-25 10:07 AM, Richard Purdie wrote:
> If we don't do this, the deploy sstate object contains an every
> increasing number of modules tarballs and kernel images, one per
> execution of "-c deploy -f".
>
Stupid question, since my sstate/deploy foo is weak at times.
Does this mean that only a single set of modules + kernel images
will be in tmp/deploy ? Or is it only sstate that is being
cleaned ?
I sometimes need multiple copies around for debug purposes, so
I'm wondering if that is still possible with this change ?
Bruce
> Cleaning the directory before we start makes things much tidier.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index dee6f7d..f37affc 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -511,6 +511,7 @@ kernel_do_deploy() {
> ln -sf ${initramfs_base_name}.bin ${initramfs_symlink_name}.bin
> fi
> }
> +do_deploy[cleandirs] = "${DEPLOYDIR}"
> do_deploy[dirs] = "${DEPLOYDIR} ${B}"
> do_deploy[prefuncs] += "package_get_auto_pr"
>
>
>
next prev parent reply other threads:[~2016-01-25 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:07 [PATCH] kernel: Clean DEPLOYDIR before do_deploy runs Richard Purdie
2016-01-25 15:47 ` Bruce Ashfield [this message]
2016-01-25 15:52 ` Richard Purdie
2016-01-25 16:14 ` Bruce Ashfield
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=56A64385.1020804@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox