From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 next] package/tar: bump target version to 1.32 (host is kept at 1.29)
Date: Sat, 18 Jan 2020 15:51:54 +0100 [thread overview]
Message-ID: <20200118145154.GC22540@scaer> (raw)
In-Reply-To: <CAJ4jsae+9emfBSo1x9CHsNszj62fMx6Su-Jixp_OsbJbYL4ucw@mail.gmail.com>
Carlos, All,
On 2020-01-18 11:12 -0300, Carlos Santos spake thusly:
> On Sat, Jan 18, 2020 at 9:39 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2019-11-19 09:18 -0300, unixmania at gmail.com spake thusly:
> > > From: Luc Creti <luc.creti@atos.net>
[--SNIP--]
> > > Hence host-tar must be kept at version 1.29.
[--SNIP--]
> > Applied to master, with all the host-related commentsd and variables
> > moved down to gether. Thanks.
> Can't we at least get rid of the cpio thing, as done in v5?
Why? We can't ensure that the host has tar, and if it does, we can't be
sure we can rely on it to extract the tarball.
cpio is present virtually everywhere, and its format has been stable for
the longest time.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-01-18 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 12:18 [Buildroot] [PATCH v3 next] package/tar: bump target version to 1.32 (host is kept at 1.29) unixmania at gmail.com
2020-01-18 12:39 ` Yann E. MORIN
2020-01-18 14:12 ` Carlos Santos
2020-01-18 14:51 ` Yann E. MORIN [this message]
2020-01-18 20:22 ` Carlos Santos
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=20200118145154.GC22540@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.