From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/8 v4] support/download: add possibility to not fail on missing hash
Date: Tue, 14 Apr 2015 01:43:40 +0200 [thread overview]
Message-ID: <552C54AC.9050905@mind.be> (raw)
In-Reply-To: <1f4a021bb2826f296ae7b2876f8ae8ab57cde349.1428512075.git.yann.morin.1998@free.fr>
On 08/04/15 18:57, Yann E. MORIN wrote:
> In very constrained cases, it might be needed to not fail if a hash is
> missing. This is notably the case for custom external toolchains to be
> downloaded, because we do have a .hash file for external toolchains,
> but we oviously can not have hashes for all existing cutom toolchains
obviously custom
> (he, "custom"!).
So what is it going to be cutom or custom? :-)
>
> So, add a way to avoid failing in that case.
>
> Form the Makefile, we export the list of files for which not to check
From
> the hash. Then, from the check-hash script, if no check was done, and
> the file we were trying to match in in this exclusion list, we just exit
is
> without error.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Cc: Arnout Vandecappelle <arnout@mind.be>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
but more fixes below...
>
> ---
> Changes v3 -> v4:
> - drop the magic value, use a list of excluded files (Arnout)
>
> Changes v1 -> v2:
> - fix typoes in commit log
> ---
> package/pkg-download.mk | 3 +++
> support/download/check-hash | 5 +++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/package/pkg-download.mk b/package/pkg-download.mk
> index e274712..5b7c861 100644
> --- a/package/pkg-download.mk
> +++ b/package/pkg-download.mk
> @@ -60,6 +60,9 @@ domainseparator = $(if $(1),$(1),/)
> # github(user,package,version): returns site of GitHub repository
> github = https://github.com/$(1)/$(2)/archive/$(3)
>
> +# Expressely do not check hashes for those files
Expressly
> +export BR_NO_CHECK_HASH_FOR
> +
> ################################################################################
> # The DOWNLOAD_* helpers are in charge of getting a working copy
> # of the source repository for their corresponding SCM,
> diff --git a/support/download/check-hash b/support/download/check-hash
> index d37f1cd..ca81f00 100755
> --- a/support/download/check-hash
> +++ b/support/download/check-hash
> @@ -99,6 +99,11 @@ while read t h f; do
> done <"${h_file}"
>
> if [ ${nb_checks} -eq 0 ]; then
> + for f in ${BR_NO_CHECK_HASH_FOR}; do
> + if [ "${f}" = "${base}" ]; then
> + exit 0
> + fi
> + done
I can't stop myself from micro-optimising :-)
if [ ${nb_checks} -eq 0 ]; then
case " ${BR_NO_CHECK_HASH_FOR} " in
"* ${base} *")
exit 0
;;
esac
printf "ERROR: No hash found for %s\n" "${base}" >&2
exit 0
fi
But maybe that's not really more readable...
Regards,
Arnout
> printf "ERROR: No hash found for %s\n" "${base}" >&2
> exit 0
> fi
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-04-13 23:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 16:57 [Buildroot] [PATCH 0/8 v4] toolchain: better handle hashes (branch yem/dl-hash-toolchains) Yann E. MORIN
2015-04-08 16:57 ` [Buildroot] [PATCH 1/8 v4] package/gcc: add hashes Yann E. MORIN
2015-04-13 23:32 ` Arnout Vandecappelle
2015-04-19 9:13 ` Yann E. MORIN
2015-04-08 16:57 ` [Buildroot] [PATCH 2/8 v4] package/binutils: " Yann E. MORIN
2015-04-13 23:35 ` Arnout Vandecappelle
2015-04-08 16:57 ` [Buildroot] [PATCH 3/8 v4] package/uclibc: add missing hash for eXtensa Yann E. MORIN
2015-04-13 23:36 ` Arnout Vandecappelle
2015-04-08 16:57 ` [Buildroot] [PATCH 4/8 v4] support/download: add possibility to not fail on missing hash Yann E. MORIN
2015-04-13 23:43 ` Arnout Vandecappelle [this message]
2015-04-19 9:42 ` Yann E. MORIN
2015-04-08 16:57 ` [Buildroot] [PATCH 5/8 v4] toolchain/external: ignore missing hash for custom downloaded toolchain Yann E. MORIN
2015-04-13 23:44 ` Arnout Vandecappelle
2015-04-08 16:57 ` [Buildroot] [PATCH 6/8 v4] package/uclibc: ignore missing hash for snapshots Yann E. MORIN
2015-04-13 23:45 ` Arnout Vandecappelle
2015-04-08 16:57 ` [Buildroot] [PATCH 7/8 v4] support/download: restore mandatory check of hashes Yann E. MORIN
2015-04-13 23:46 ` Arnout Vandecappelle
2015-04-08 16:57 ` [Buildroot] [PATCH 8/8 v4] support/download: do not accept exlcuded files with ashes Yann E. MORIN
2015-04-13 23:56 ` Arnout Vandecappelle
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=552C54AC.9050905@mind.be \
--to=arnout@mind.be \
--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