Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/3] qt5serialbus: fix 5.6.3 license file hashes
Date: Wed, 3 Oct 2018 14:49:44 +0200	[thread overview]
Message-ID: <20181003144944.2a26cf25@windsurf> (raw)
In-Reply-To: <20181003045224.wlrhhkgyv2tj3pqg@sapphire.tkos.co.il>

Hello,

On Wed, 3 Oct 2018 07:52:24 +0300, Baruch Siach wrote:

> Shouldn't the tarball hash move also here? Having the 5.6.x tarball hash in 
> the default .hash file is confusing.

This doesn't work, because the download wrapper only uses the main hash
file:

define DOWNLOAD
        $(Q)mkdir -p $($(PKG)_DL_DIR)
        $(Q)$(EXTRA_ENV) $(FLOCK) $(DL_WRAPPER) \
                -c '$($(PKG)_DL_VERSION)' \
                -d '$($(PKG)_DL_DIR)' \
                -D '$(DL_DIR)' \
                -f '$(notdir $(1))' \
                -H '$(PKGDIR)/$($(PKG)_RAWNAME).hash' \
                -n '$($(PKG)_BASENAME_RAW)' \
                -N '$($(PKG)_RAWNAME)' \
                -o '$($(PKG)_DL_DIR)/$(notdir $(1))' \
                $(if $($(PKG)_GIT_SUBMODULES),-r) \
                $(DOWNLOAD_URIS) \
                $(QUIET) \
                -- \
                $($(PKG)_DL_OPTS)
endef

See the value passed to the -H option. It works for license files
because:

define legal-license-file # pkgname, pkgname-pkgver, pkgdir, filename, file-fullpath, {HOST|TARGET}
	mkdir -p $(LICENSE_FILES_DIR_$(6))/$(2)/$(dir $(4)) && \
	{ \
		if [ -f $(3)/$($(PKG)_VERSION)/$(1).hash ]; then \
			support/download/check-hash $(3)/$($(PKG)_VERSION)/$(1).hash $(5) $(4); \
		else \
			support/download/check-hash $(3)/$(1).hash $(5) $(4); \
		fi; \
		case $${?} in (0|3) ;; (*) exit 1;; esac; \
	} && \
	cp $(5) $(LICENSE_FILES_DIR_$(6))/$(2)/$(4)
endef

I discussed this topic on the mailing list a few weeks ago with Yann.
See
http://lists.busybox.net/pipermail/buildroot/2018-September/229892.html
and
http://lists.busybox.net/pipermail/buildroot/2018-September/230404.html.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-10-03 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 21:16 [Buildroot] [PATCH v1 1/3] qt5connectivity: add license files hashes Peter Seiderer
2018-10-02 21:16 ` [Buildroot] [PATCH v1 2/3] qt5serialbus: fix 5.6.3 license file hashes Peter Seiderer
2018-10-03  4:52   ` Baruch Siach
2018-10-03 12:49     ` Thomas Petazzoni [this message]
2018-10-05 16:09       ` Yann E. MORIN
2018-10-09  7:46   ` Thomas Petazzoni
2018-10-02 21:16 ` [Buildroot] [PATCH v1 3/3] qt5serialport: " Peter Seiderer
2018-10-09  7:47   ` Thomas Petazzoni
2018-10-09  7:19 ` [Buildroot] [PATCH v1 1/3] qt5connectivity: add license files hashes Thomas Petazzoni

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=20181003144944.2a26cf25@windsurf \
    --to=thomas.petazzoni@bootlin.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