All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Dmitry Goldin <dgoldin+lkml@protonmail.ch>,
	linux-kernel@vger.kernel.org, Sam James <sam@gentoo.org>
Subject: Re: [PATCH] kheaders: prefer gtar over tar for better compatibility
Date: Sun, 25 Dec 2022 17:33:15 +0100	[thread overview]
Message-ID: <628c5e32a437ad198866b03f2d6ff8a9c65754df.camel@gentoo.org> (raw)
In-Reply-To: <CAK7LNAQ8=YbOVvugBUQBo8eXRMH+YA49aS-1C=2hCGq0xoW7XA@mail.gmail.com>

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


  reply	other threads:[~2022-12-25 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17  8:41 [PATCH] kheaders: prefer gtar over tar for better compatibility Michał Górny
2022-12-24 16:45 ` Masahiro Yamada
2022-12-25 16:33   ` Michał Górny [this message]
2023-01-17 19:01     ` Sam James
2023-02-04 16:39       ` Sam James
2023-03-17  0:04         ` Sam James
2023-03-19  7:43           ` Masahiro Yamada
2023-04-12  8:27             ` [PATCH v2] kheaders: make it possible to override TAR Michał Górny
2025-07-19 15:24               ` [PATCH v3] " Sam James
2025-07-19 20:10                 ` Nathan Chancellor
2025-07-20 19:08                   ` Michał Górny
2025-07-20 19:59                     ` Nicolas Schier
2025-07-26  6:46                     ` Masahiro Yamada

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=628c5e32a437ad198866b03f2d6ff8a9c65754df.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=dgoldin+lkml@protonmail.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@gentoo.org \
    --cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.