From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] u-boot: Add sha256 hash value for earlier 2013.10 version.
Date: Tue, 21 Apr 2015 13:35:25 +0200 [thread overview]
Message-ID: <20150421133525.0589481e@free-electrons.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1504191245070.8977@localhost>
Dear Robert P. J. Day,
On Sun, 19 Apr 2015 12:49:26 -0400 (EDT), Robert P. J. Day wrote:
>
> Add a hash value for u-boot-2013.10.tar.bz2.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> if i understand this correctly, if a package has no hash file, then
> downloading generates a warning. but with the newly-added uboot.hash
> file, the missing sha256sum for the earlier 2013.10 version generates
> an "ERROR" when running "make source", even though the tarball is in
> fact downloaded correctly. so just add a hash value to quiet the
> download.
Nope, that's not the right way of doing things. First and foremost, a
missing hash in the hash file is currently not a hard failure, only a
warning. It will be turned into a hard failure soon, but with
appropriate handling of custom versions (see the patch series being
sent by Yann E. Morin and Arnout Vandecappelle about this).
The problem with your patch is that it adds just the hash file 2013.10.
What about the dozens of other U-Boot releases? And the zillions of
U-Boot forks all over the place?
Since it doesn't scale, we're going t keep it is simple: a hash for the
default U-Boot version currently used by Buildroot, and that's it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-04-21 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 16:49 [Buildroot] [PATCH] u-boot: Add sha256 hash value for earlier 2013.10 version Robert P. J. Day
2015-04-21 11:35 ` Thomas Petazzoni [this message]
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=20150421133525.0589481e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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