Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Joshua Watt" <JPEWhacker@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH] bitbake.conf: Add lz4c, pzstd and zstd
Date: Wed, 14 Jul 2021 08:51:29 -0500	[thread overview]
Message-ID: <853bb8c3-6bc9-a154-613c-c5dfbfbb89ba@gmail.com> (raw)
In-Reply-To: <CANNYZj8QESeodwNfdV1Ve4GzfW5tQkLTtNA5qac1jt09wW5OMA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]

On 7/14/21 8:45 AM, Alexander Kanavin wrote:
> While I welcome the transition to zstd, I think the commit message 
> needs to be more descriptive. Needed by bitbake where and how? Is 
> there some patchset upcoming?


Ya, this is necessary for the patch: 
https://lists.openembedded.org/g/bitbake-devel/message/12385, which 
isn't merged yet.


>
> Alex
>
> On Wed, 14 Jul 2021 at 15:42, Joshua Watt <JPEWhacker@gmail.com 
> <mailto:JPEWhacker@gmail.com>> wrote:
>
>     Adds the command line compression tools which are needed by bitbake
>
>     Signed-off-by: Joshua Watt <JPEWhacker@gmail.com
>     <mailto:JPEWhacker@gmail.com>>
>     ---
>      meta/conf/bitbake.conf | 6 +++---
>      1 file changed, 3 insertions(+), 3 deletions(-)
>
>     diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
>     index f451ba6a47..3801db7d42 100644
>     --- a/meta/conf/bitbake.conf
>     +++ b/meta/conf/bitbake.conf
>     @@ -484,12 +484,12 @@ HOSTTOOLS += " \
>          [ ar as awk basename bash bzip2 cat chgrp chmod chown chrpath
>     cmp comm cp cpio \
>          cpp cut date dd diff diffstat dirname du echo egrep env
>     expand expr false \
>          fgrep file find flock g++ gawk gcc getconf getopt git grep
>     gunzip gzip \
>     -    head hostname iconv id install ld ldd ln ls make md5sum mkdir
>     mkfifo mknod \
>     +    head hostname iconv id install ld ldd ln ls lz4c make md5sum
>     mkdir mkfifo mknod \
>          mktemp mv nm objcopy objdump od patch perl pr printf pwd \
>     -    python3 ranlib readelf readlink realpath rm rmdir rpcgen sed
>     seq sh \
>     +    python3 pzstd ranlib readelf readlink realpath rm rmdir
>     rpcgen sed seq sh \
>          sha1sum sha224sum sha256sum sha384sum sha512sum \
>          sleep sort split stat strings strip tail tar tee test touch
>     tr true uname \
>     -    uniq wc wget which xargs \
>     +    uniq wc wget which xargs zstd \
>      "
>
>      # Tools needed to run testimage runtime image testing
>     -- 
>     2.32.0
>
>
>     
>

[-- Attachment #2: Type: text/html, Size: 3751 bytes --]

  reply	other threads:[~2021-07-14 13:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 13:42 [OE-core][PATCH] bitbake.conf: Add lz4c, pzstd and zstd Joshua Watt
2021-07-14 13:45 ` Alexander Kanavin
2021-07-14 13:51   ` Joshua Watt [this message]
2021-07-14 13:56     ` Alexander Kanavin
2021-08-14 18:35 ` Alexandre Belloni
2021-08-16 15:49 ` Khem Raj
2021-08-16 16:14 ` Khem Raj
2021-08-18 22:19   ` Randy MacLeod
2021-08-19 14:50     ` Konrad Weihmann
2021-08-19 15:07       ` Leon Woestenberg
2021-08-19 16:06       ` Richard Purdie
2021-08-19 16:31         ` Konrad Weihmann
2021-08-19 16:34           ` Joshua Watt
2021-08-19 16:40           ` Richard Purdie

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=853bb8c3-6bc9-a154-613c-c5dfbfbb89ba@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=alex.kanavin@gmail.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