Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Markus Lehtonen <markus.lehtonen@linux.intel.com>,
	openembedded-core@lists.openembedded.org,
	Ross Burton <ross.burton@intel.com>
Subject: Re: [PATCH v2] base.bbclass wipe ${S} before unpacking source
Date: Tue, 22 Mar 2016 07:47:51 +0000	[thread overview]
Message-ID: <1458632871.20442.26.camel@linuxfoundation.org> (raw)
In-Reply-To: <1458631473-22563-2-git-send-email-markus.lehtonen@linux.intel.com>

On Tue, 2016-03-22 at 09:24 +0200, Markus Lehtonen wrote:
> Make sure that we have a pristine source tree after do_unpack.
> 
> [YOCTO #9064]
> 
> Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
> ---
>  meta/classes/base.bbclass | 12 ++----------
>  1 file changed, 2 insertions(+), 10 deletions(-)
> 
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index 1372f38..aa107d4 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -133,23 +133,15 @@ python base_do_fetch() {
>  
>  addtask unpack after do_fetch
>  do_unpack[dirs] = "${WORKDIR}"
> +do_unpack[cleandirs] = "${@d.getVar('S', True) if d.getVar('S',
> True) != d.getVar('WORKDIR', True) else ''}"

Should this be else '${S}/patches'?

If we don't do that, there might be a case where we don't clean up the
patches directory when we could/should compared to the existing code?

Cheers,

Richard


  reply	other threads:[~2016-03-22  7:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22  7:24 [PATCH v2] Add ${S} to do_unpack[cleandirs] Markus Lehtonen
2016-03-22  7:24 ` [PATCH v2] base.bbclass wipe ${S} before unpacking source Markus Lehtonen
2016-03-22  7:47   ` Richard Purdie [this message]
2016-03-22 16:45     ` Markus Lehtonen

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=1458632871.20442.26.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=markus.lehtonen@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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