From: Tom Rini <tom_rini@mentor.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/1] Add unzip DEPENDS for .zip SRC_URI files
Date: Fri, 15 Jul 2011 10:35:21 -0700 [thread overview]
Message-ID: <cover.1310751195.git.tom_rini@mentor.com> (raw)
Hey all,
In doing some world builds I ran into "oops, we don't make .zip files
depend on unzip-native". So this is a port of the commit from oe.dev
that does this.
v2: Don brown paper bag, s/do_populate_staging/do_populate_sysroot, test
The following changes since commit e66c2999afa2b3efbce8bb46c89f9db5e15f35c7:
Saul Wold (1):
libx11: ensure nativesdk uses correct DEPENDS and XCB flags
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib trini/add-zip-native-check
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=trini/add-zip-native-check
Ihar Hrachyshka (1):
Fixed concurrency problem for ZIP packed recipes.
meta/classes/base.bbclass | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
next reply other threads:[~2011-07-15 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 17:35 Tom Rini [this message]
2011-07-15 17:35 ` [PATCH v2 1/1] Fixed concurrency problem for ZIP packed recipes Tom Rini
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=cover.1310751195.git.tom_rini@mentor.com \
--to=tom_rini@mentor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox