From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Matthew McClintock <msm@freescale.com>
Subject: Re: [PATCH 1/2] bitbake/fetch2: add support for wrapper command
Date: Sun, 15 Jan 2012 20:53:15 -0800 [thread overview]
Message-ID: <4F13AD3B.50902@linux.intel.com> (raw)
In-Reply-To: <1326409412-15507-1-git-send-email-msm@freescale.com>
On 01/12/2012 03:03 PM, Matthew McClintock wrote:
> cc: bitbake-devel@lists.openembedded.org
> Signed-off-by: Matthew McClintock<msm@freescale.com>
> ---
> bitbake/lib/bb/fetch2/__init__.py | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/bitbake/lib/bb/fetch2/__init__.py b/bitbake/lib/bb/fetch2/__init__.py
> index 3af56e5..1d7d5c7 100644
> --- a/bitbake/lib/bb/fetch2/__init__.py
> +++ b/bitbake/lib/bb/fetch2/__init__.py
> @@ -389,6 +389,8 @@ def runfetchcmd(cmd, d, quiet = False, cleanup = []):
> Optionally remove the files/directories listed in cleanup upon failure
> """
>
> + cmd = "%s %s" % (bb.data.getVar("BB_FETCH_WRAPPER", d, True), cmd)
> +
I am guessing you really want a check here if BB_FETCH_WRAPPER is set,
otherwise I am not sure this will work correctly, did you test without
this new variable set?
Sau!
> # Need to export PATH as binary could be in metadata paths
> # rather than host provided
> # Also include some other variables.
next prev parent reply other threads:[~2012-01-16 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 23:03 [PATCH 1/2] bitbake/fetch2: add support for wrapper command Matthew McClintock
2012-01-12 23:03 ` [PATCH 2/2] " Matthew McClintock
2012-01-16 4:53 ` Saul Wold [this message]
2012-01-16 12:32 ` [PATCH 1/2] " Richard Purdie
2012-01-16 15:05 ` McClintock Matthew-B29882
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=4F13AD3B.50902@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=msm@freescale.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 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.