From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/7 v5] support/download: add possibility to not fail on missing hash
Date: Sun, 19 Apr 2015 19:41:23 +0200 [thread overview]
Message-ID: <5533E8C3.5090006@mind.be> (raw)
In-Reply-To: <942ffe13728f4ab40af2ab19d9fe9a256647bcfa.1429447148.git.yann.morin.1998@free.fr>
On 19/04/15 14:44, 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 obviously can not have hashes for all existing custom toolchains
> (he, "custom"!).
>
> So, add a way to avoid failing in that case.
>
>>From the Makefile, we export the list of files for which not to check
> 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
> 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>
Ouch, it doesn't work...
>
> ---
> Changes v4 -> v5:
> - micro-optimisation, use case-esac instead of a for-loop (Arnout)
> - typoes (Arnout)
>
> 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 | 6 ++++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/package/pkg-download.mk b/package/pkg-download.mk
> index e274712..1fc23c4 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)
>
> +# Expressly do not check hashes for those files
> +export BR_NO_CHECK_HASH_FOR
The comment is not very clear. Perhaps
# Files in this variable do not get their hash checked.
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 678a7ef..1280322 100755
> --- a/support/download/check-hash
> +++ b/support/download/check-hash
> @@ -99,6 +99,12 @@ while read t h f; do
> done <"${h_file}"
>
> if [ ${nb_checks} -eq 0 ]; then
> + case " ${BR_NO_CHECK_HASH_FOR} " in
> + " ${base} ")
This does not work. If there is more than one file, there can be something
before/after ${base}, so we need to add * at the beginning and the end. But
then, the quotes stop the matching of *, so we have to write:
*\ ${base}\ *)
Regards,
Arnout
> + # File explicitly has no hash
> + exit 0
> + ;;
> + esac
> 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-19 17:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 12:44 [Buildroot] [PATCH 0/7 v5] toolchain: better handle hashes (branch yem/dl-hash-toolchains) Yann E. MORIN
2015-04-19 12:44 ` [Buildroot] [PATCH 1/7 v5] package/gcc: add hashes Yann E. MORIN
2015-04-19 16:41 ` Arnout Vandecappelle
2015-04-19 12:44 ` [Buildroot] [PATCH 2/7 v5] package/binutils: " Yann E. MORIN
2015-04-19 16:42 ` Arnout Vandecappelle
2015-04-19 12:44 ` [Buildroot] [PATCH 3/7 v5] package/uclibc: add missing hash for eXtensa Yann E. MORIN
2015-04-19 16:47 ` Arnout Vandecappelle
2015-04-19 16:57 ` [Buildroot] [PATCH] uclibc: update hash for arc Arnout Vandecappelle
2015-04-19 17:03 ` [Buildroot] [PATCH 3/7 v5] package/uclibc: add missing hash for eXtensa Yann E. MORIN
2015-04-19 12:44 ` [Buildroot] [PATCH 4/7 v5] support/download: add possibility to not fail on missing hash Yann E. MORIN
2015-04-19 17:41 ` Arnout Vandecappelle [this message]
2015-04-19 12:44 ` [Buildroot] [PATCH 5/7 v5] toolchain/external: ignore missing hash for custom downloaded toolchain Yann E. MORIN
2015-04-19 12:44 ` [Buildroot] [PATCH 6/7 v5] package/uclibc: ignore missing hash for snapshots Yann E. MORIN
2015-04-19 17:46 ` Arnout Vandecappelle
2015-04-19 12:45 ` [Buildroot] [PATCH 7/7 v5] support/download: restore mandatory check of hashes Yann E. MORIN
2015-04-19 17:54 ` Arnout Vandecappelle
2015-04-19 17:55 ` [Buildroot] [PATCH v6 1/8] package/gcc: add hashes Arnout Vandecappelle
2015-04-19 17:55 ` [Buildroot] [PATCH v6 2/8] package/binutils: " Arnout Vandecappelle
2015-04-19 17:55 ` [Buildroot] [PATCH v6 3/8] package/uclibc: add missing hash for eXtensa Arnout Vandecappelle
2015-04-19 17:55 ` [Buildroot] [PATCH v6 4/8] uclibc: update hash for arc Arnout Vandecappelle
2015-04-19 18:28 ` Yann E. MORIN
2015-04-19 17:55 ` [Buildroot] [PATCH v6 5/8] support/download: add possibility to not fail on missing hash Arnout Vandecappelle
2015-04-19 18:38 ` Yann E. MORIN
2015-04-20 7:45 ` Arnout Vandecappelle
2015-04-20 21:24 ` Yann E. MORIN
2015-04-19 17:55 ` [Buildroot] [PATCH v6 6/8] toolchain/external: ignore missing hash for custom downloaded toolchain Arnout Vandecappelle
2015-04-19 17:55 ` [Buildroot] [PATCH v6 7/8] package/uclibc: ignore missing hash for snapshots Arnout Vandecappelle
2015-04-19 17:55 ` [Buildroot] [PATCH v6 8/8] support/download: restore mandatory check of hashes 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=5533E8C3.5090006@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 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.