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?

Alex

On Wed, 14 Jul 2021 at 15:42, Joshua Watt <JPEWhacker@gmail.com> wrote:

> Adds the command line compression tools which are needed by bitbake
>
> Signed-off-by: Joshua Watt <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
>
>
> 
>
>