From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base.bbclass: If unpacking again, wipe out ${S}/patches
Date: Fri, 02 Mar 2012 12:39:30 +0000 [thread overview]
Message-ID: <1330691970.15224.18.camel@ted> (raw)
In-Reply-To: <F32A162F-E406-4D75-8BE5-E742C27E2E95@dominion.thruhere.net>
On Fri, 2012-03-02 at 13:29 +0100, Koen Kooi wrote:
> Op 2 mrt. 2012, om 13:10 heeft Richard Purdie het volgende geschreven:
>
> > If we unpack again, its assumed the data in any patches directory is invalid
> > since do_patch will run again. This ensures old patch data doesn't get
> > reused in a confused way.
> >
> > Ideally we should probably wipe out ${S} here but that is probably a change
> > for another time.
> >
> > [YOCTO #2043 partially]
> >
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> > diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> > index a76fe55..39d3e78 100644
> > --- a/meta/classes/base.bbclass
> > +++ b/meta/classes/base.bbclass
> > @@ -94,6 +94,7 @@ python base_do_fetch() {
> >
> > addtask unpack after do_fetch
> > do_unpack[dirs] = "${WORKDIR}"
> > +do_unpack[cleandirs] = "${S}/patches"
>
> This gets clean *before* do_unpack, right? I have a number of recipes
> that use sources with patches/ as a toplevel subdirectory.
Yes, bitbake wipes out cleandirs before the task runs. As I mention, we
could in theory wipe ${S} there, I'm just a little more nervous about
that change.
Cheers,
Richard
prev parent reply other threads:[~2012-03-02 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:10 [PATCH] base.bbclass: If unpacking again, wipe out ${S}/patches Richard Purdie
2012-03-02 12:29 ` Koen Kooi
2012-03-02 12:39 ` Richard Purdie [this message]
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=1330691970.15224.18.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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.