linux-kernel - Re: [PATCH] kheaders: prefer gtar over tar for better compatibility

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <628c5e32a437ad198866b03f2d6ff8a9c65754df.camel@gentoo.org>
Date:   Sun, 25 Dec 2022 17:33:15 +0100
From:   Michał Górny <mgorny@...too.org>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     Dmitry Goldin <dgoldin+lkml@...tonmail.ch>,
        linux-kernel@...r.kernel.org, Sam James <sam@...too.org>
Subject: Re: [PATCH] kheaders: prefer gtar over tar for better compatibility

On Sun, 2022-12-25 at 01:45 +0900, Masahiro Yamada wrote:
> Instead of inserting a workaround like this,
> another way is to allow users to override a variable
> from the command line.
> 
> 
> See the top Makefile, for example,
> 
> 
> AWK             = awk
> 
> 
> Then, users can do "make AWK=gawk"

I'm sorry but are you requesting that I remove the check and use $TAR
instead, or allow overriding with TAR, and fall back to gtar or tar
respectively?  If the former, should the script unconditionally assume
that TAR will be always set in the environment, or include fallback to
tar for when the script is run directly?

> 
-- 
Best regards,
Michał Górny