From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/6 v3] toolchain/external: ignore missing hash for custom downloaded toolchain
Date: Tue, 7 Apr 2015 23:51:47 +0200 [thread overview]
Message-ID: <20150407215147.GU4216@free.fr> (raw)
In-Reply-To: <552315BA.3010605@mind.be>
Arnout, All,
On 2015-04-07 01:24 +0200, Arnout Vandecappelle spake thusly:
> On 06/04/15 23:20, Yann E. MORIN wrote:
> > On 2015-04-06 23:03 +0200, Arnout Vandecappelle spake thusly:
> >> On 06/04/15 14:13, Yann E. MORIN wrote:
[--SNIP--]
> >>> +# Magic value to tell the download helper to avoid failling on missing hash
> >>> +export BR_MISSING_HASH_OK := $(call ignore-missing-hash-magic,$(TOOLCHAIN_EXTERNAL_SOURCE))
> >> Urgh - this disables the hash check for all packages, not just the toolchain.
> >
> > No, that disable the check only for that one file, because we're not
> > chcking whether it is set, but whether it is set to the correct value
> > (i.e. the sha1 of the filename).
>
> Ah of course, that's probably why you introduced that.
>
> But it does mean that only a single file can ever be bypassed...
Right.
[--SNIP--]
> >> hasharg = $(if $(filter-out $(TOOLCHAIN_EXTERNAL_SOURCE),$(1)),
> > You probably meant s/TOOLCHAIN_EXTERNAL_SOURCE/NOHASH_FILES/ ?
> Untested and all :-)
Hehe! :-)
> >> -H $(PKGDIR)/$($(PKG)_RAWNAME).hash)
> >>
> >> define DOWNLOAD_WGET
> >> $(EXTRA_ENV) $(DL_WRAPPER) -b wget \
> >> -o $(DL_DIR)/$(2) \
> >> $(call hasharg,$(2)) \
> >> $(QUIET) \
> >> -- \
> >> '$(call qstrip,$(1))'
> >> endef
> >>
> >> (all completely untested, obviously :-)
> >
> > Well, that sounds a bit better than my proposal.
> >
> > Still, I prefer:
> >
> > - we offload the check in the dl-wrapper so we can do the check in a
> > single place, rather than re-add extra code in each download macros
> > (the dl-wrapper was added because the Makefile macros were too
> > complex to handle);
> Ack that, though I don't immediately see a way to do that.
Don;t worry, I'll find a way... ;-]
> > - we pass obscur values (like a sha1), rather than the filenames, to
> > make it even less easy to use.
>
> I really don't see the point of that... If it's not documented, you have to
> look at the source code to find out which variable to set. And when you look at
> the source code, you immediately see how this obscure value is calculated so it
> makes no real difference.
OK, makes sense.
I will rework the series accordingly. Thanks for the suggestions!
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:[~2015-04-07 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 12:13 [Buildroot] [PATCH 0/6 v3] toolchain: better handle hashes (branch yem/dl-hash-toolchains) Yann E. MORIN
2015-04-06 12:13 ` [Buildroot] [PATCH 1/6 v3] support/download: do not warn about missing hash file for repositories Yann E. MORIN
2015-04-06 14:39 ` Arnout Vandecappelle
2015-04-06 21:29 ` Thomas Petazzoni
2015-04-06 12:13 ` [Buildroot] [PATCH 2/6 v3] package/gcc: add hashes Yann E. MORIN
2015-04-06 12:13 ` [Buildroot] [PATCH 3/6 v3] package/binutils: " Yann E. MORIN
2015-04-06 12:13 ` [Buildroot] [PATCH 4/6 v3] support/download: add possibility to not fail on missing hash Yann E. MORIN
2015-04-06 20:47 ` Arnout Vandecappelle
2015-04-06 12:13 ` [Buildroot] [PATCH 5/6 v3] toolchain/external: ignore missing hash for custom downloaded toolchain Yann E. MORIN
2015-04-06 21:03 ` Arnout Vandecappelle
2015-04-06 21:20 ` Yann E. MORIN
2015-04-06 23:24 ` Arnout Vandecappelle
2015-04-07 21:51 ` Yann E. MORIN [this message]
2015-04-06 12:13 ` [Buildroot] [PATCH 6/6 v3] support/download: restore mandatory check of hashes Yann E. MORIN
2015-04-06 21:05 ` Arnout Vandecappelle
2015-04-07 22:04 ` Yann E. MORIN
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=20150407215147.GU4216@free.fr \
--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.