From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: "Martin Zeiser \(mzeiser\)" <mzeiser@cisco.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/4] support/download: teach dl-wrapper to handle more than one hash file
Date: Mon, 06 Nov 2023 18:41:01 +0100 [thread overview]
Message-ID: <87fs1iye36.fsf@48ers.dk> (raw)
In-Reply-To: <87jzqvxm40.fsf@48ers.dk> (Peter Korsgaard's message of "Mon, 06 Nov 2023 10:33:03 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>> Currently, we expect and only use hash files that lie within the package
>> directory, alongside the .mk file. Those hash files are thus bundeld
> s/bundeld/bundled/
> Committed with that fixed, thanks.
Actually not. As discussed on IRC, we also need to update the get-hash
call for license files.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-06 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 21:09 [Buildroot] [PATCH 0/4] support/download: accept user-provided list of extra hash files (branch yem/multi-hash) Yann E. MORIN
2023-10-28 21:09 ` [Buildroot] [PATCH 1/4] docs/manual: svn downloads can be hash-checked Yann E. MORIN
2023-11-05 20:41 ` Peter Korsgaard
2023-11-09 17:22 ` Peter Korsgaard
2023-10-28 21:09 ` [Buildroot] [PATCH 2/4] support/download: teach dl-wrapper to handle more than one hash file Yann E. MORIN
2023-11-06 9:33 ` Peter Korsgaard
2023-11-06 17:41 ` Peter Korsgaard [this message]
2023-10-28 21:09 ` [Buildroot] [PATCH 3/4] package/pkg-download: lookup hash files in global-patch-dir Yann E. MORIN
2023-10-28 21:09 ` [Buildroot] [PATCH 4/4] pkg-download: add option to enforce hash checking 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=87fs1iye36.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=mzeiser@cisco.com \
--cc=yann.morin.1998@free.fr \
/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