From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Elizabeth 'pidge' Flanagan" <pidge@toganlabs.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] bitbake.conf: Add aws-cli support
Date: Tue, 28 Mar 2017 14:34:54 +0100 [thread overview]
Message-ID: <1490708094.13980.286.camel@linuxfoundation.org> (raw)
In-Reply-To: <1490701251-20408-2-git-send-email-pidge@toganlabs.com>
On Tue, 2017-03-28 at 13:40 +0200, Elizabeth 'pidge' Flanagan wrote:
> This commit adds aws-cli support to bitbake in order to support
> the s3 fetcher in bitbake.
>
> Signed-off-by: Elizabeth 'pidge' Flanagan <pidge@toganlabs.com>
> ---
> meta/conf/bitbake.conf | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index fa5445b..f21b8d3 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -458,8 +458,8 @@ HOSTTOOLS += " \
> bash sh cut sed gcc ld git rm install which find xargs cat true mktemp \
> grep tar gzip touch cp mv basename dirname tr getopt sort awk head tail \
> mkdir patch uniq perl python chmod python3 ar strip expr ls make as \
> - ranlib egrep echo chown cpio tee wc wget bzip2 stat date rmdir od diff \
> - md5sum dd chrpath file pod2man gunzip python2.7 ln g++ [ false true \
> + ranlib egrep echo chown cpio tee wc wget aws bzip2 stat date rmdir \
> + od diff md5sum dd chrpath file pod2man gunzip python2.7 ln g++ [ false true \
> uname test hostname nm objdump objcopy cmp printf env readlink gawk fgrep \
> expand pwd sleep diffstat chgrp flock ldd strings rpcgen du makeinfo \
> getconf mknod cpp readelf split \
Adding to HOSTTOOLS means *all* systems have to have this available
else the build fails. This for example would breaks all our
autobuilders. Past feature freeze point this tends to upset me a bit
even more than usual.
You want to add this to HOSTTOOLS_NONFATAL below.
Your patch also doesn't apply against master either.
Cheers,
Richard
next prev parent reply other threads:[~2017-03-28 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 11:40 [PATCH 1/2] aws-cli_1.11.66.bb: Initial commit of aws-cli Elizabeth 'pidge' Flanagan
2017-03-28 11:40 ` [PATCH 2/2] bitbake.conf: Add aws-cli support Elizabeth 'pidge' Flanagan
2017-03-28 13:34 ` Richard Purdie [this message]
2017-03-28 12:02 ` ✗ patchtest: failure for "aws-cli_1.11.66.bb: Initial co..." and 1 more Patchwork
2017-03-28 16:50 ` [PATCH 1/2] aws-cli_1.11.66.bb: Initial commit of aws-cli Andre McCurdy
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=1490708094.13980.286.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pidge@toganlabs.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