From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] classes/package: ensure pkgdata is cleaned out first
Date: Mon, 30 Jul 2012 07:26:09 +0100 [thread overview]
Message-ID: <1343629569.16998.41.camel@ted> (raw)
In-Reply-To: <1343540484-5817-1-git-send-email-paul.eggleton@linux.intel.com>
On Sun, 2012-07-29 at 06:41 +0100, Paul Eggleton wrote:
> If do_package needs to be re-run and packages are removed/renamed as a
> result, we want the corresponding stale pkgdata files to no longer be
> present; for that we need to ensure all of the old pkgdata files are
> cleaned out prior to creating the new ones. This is particularly
> important now we rely on pkgdata more heavily (for complementary
> packages, license manifest, etc.).
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> meta/classes/package.bbclass | 1 +
> 1 file changed, 1 insertion(+)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-07-30 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 5:41 [PATCH] classes/package: ensure pkgdata is cleaned out first Paul Eggleton
2012-07-30 6:26 ` 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=1343629569.16998.41.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.