From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] linux-firmware: bump version to latest 1baa348
Date: Tue, 13 Nov 2018 21:29:46 +0100 [thread overview]
Message-ID: <20181113202946.GH10271@scaer> (raw)
In-Reply-To: <20181113210216.37879bd4@windsurf>
Thomas, All,
On 2018-11-13 21:02 +0100, Thomas Petazzoni spake thusly:
> On Tue, 13 Nov 2018 18:20:57 +0100, Marcin Niestr?j wrote:
[--SNIP--]
> > I think the overall conclusion is that a host-gzip package is needed,
> > just like host-tar. In the meantime I will send v3 of this patch with
> > proper hash (the same as you calculated above).
>
> This is getting really horrible.
>
> On my side, I have updated to Fedora 29, which ships tar 1.30, that we
> consider as broken, and therefore now for everything single small build
> that I do, I'm paying the price of building tar, which is super
> annoying. This is especially annoying as tar 1.30 is only problematic
> when *creating* tarballs of git-fetched packages, which clearly does
> not happen at every build.
Well, we only need host-tar and host-gzip when creating tarballs, not
extracting them, correct? So, we could very well envision the fact that
host-tar (and host-gzip) are only added to FOO_DOWNLOAD dependecies when
FOO_SITE_METHOD == git (and they are needed, of course), no?
(note: tar is ugly, because its configure step takes ~26s, while the
build is only ~4s).
> It would be truly horrible to also have to build our own gzip. Maybe we
> need to somehow revisit our requirement that we need to have
> reproducible tarballs for git-fetched packages ?
I am ready to pay the price for reproducibility any time.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-11-13 20:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 15:33 [Buildroot] [PATCH v2] linux-firmware: bump version to latest 1baa348 Marcin Niestroj
2018-11-09 20:57 ` Thomas Petazzoni
2018-11-09 21:06 ` Yann E. MORIN
2018-11-13 17:20 ` Marcin Niestrój
2018-11-13 17:32 ` Marcin Niestrój
2018-11-13 20:02 ` Thomas Petazzoni
2018-11-13 20:29 ` Yann E. MORIN [this message]
2018-11-13 20:57 ` Thomas Petazzoni
2018-11-13 23:54 ` Arnout Vandecappelle
2018-11-15 19:05 ` Yann E. MORIN
2018-11-16 8:35 ` Thomas Petazzoni
2018-11-20 18:50 ` Yann E. MORIN
2018-11-20 23:47 ` Arnout Vandecappelle
2018-11-21 7:13 ` Peter Korsgaard
2018-11-13 21:34 ` Marcin Niestrój
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=20181113202946.GH10271@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox