From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Joshua Lock <joshua.g.lock@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] buildtools-tarball: add tar
Date: Wed, 31 Aug 2016 00:24:25 +1200 [thread overview]
Message-ID: <2362757.E7EAftXMYC@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <81a35da5b46204d44e1d94346255b38590d49d9b.1472225461.git.joshua.g.lock@intel.com>
On Fri, 26 Aug 2016 16:43:05 Joshua Lock wrote:
> We'd like to make use of features which aren't available in tar
> versions prior to 1.27, therefore add tar to the buildtools-tarball
> so that older distributions can still perform builds.
>
> Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
> ---
> meta/recipes-core/meta/buildtools-tarball.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/meta/buildtools-tarball.bb
> b/meta/recipes-core/meta/buildtools-tarball.bb index 34df531..f28a8c3
> 100644
> --- a/meta/recipes-core/meta/buildtools-tarball.bb
> +++ b/meta/recipes-core/meta/buildtools-tarball.bb
> @@ -24,6 +24,7 @@ TOOLCHAIN_HOST_TASK ?= "\
> nativesdk-ca-certificates \
> nativesdk-texinfo \
> nativesdk-locale-base-en-us \
> + nativesdk-tar \
> "
>
> SDK_PACKAGE_ARCHS += "buildtools-dummy-${SDKPKGSUFFIX}"
Er, tar is already in buildtools-tarball... right?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2016-08-30 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 15:43 [PATCH 0/2] Preserve extended attributes in sstate objects Joshua Lock
2016-08-26 15:43 ` [PATCH 1/2] buildtools-tarball: add tar Joshua Lock
2016-08-30 12:24 ` Paul Eggleton [this message]
2016-08-26 15:43 ` [PATCH 2/2] oe.path: preserve xattr in copytree() and copyhardlinktree() Joshua Lock
2016-08-26 15:48 ` Mark Hatle
2016-08-30 12:00 ` Joshua Lock
2016-08-30 12:19 ` Richard Purdie
2016-09-06 15:22 ` Nicolas Dechesne
2016-09-06 15:26 ` Richard Purdie
2016-09-06 15:34 ` Nicolas Dechesne
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=2362757.E7EAftXMYC@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=joshua.g.lock@intel.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