Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: David Picard <david.picard@clermont.in2p3.fr>
Cc: ML_Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] how to force-check hash for extra file?
Date: Wed, 26 Mar 2025 11:06:00 +0200	[thread overview]
Message-ID: <87cye4ma9z.fsf@tarshish> (raw)
In-Reply-To: <2834e139-69b2-44e3-aceb-b8b6f44cde22@clermont.in2p3.fr> (David Picard's message of "Wed, 26 Mar 2025 09:37:35 +0100")

Hi David,

On Wed, Mar 26 2025, David Picard wrote:
> In a home-made package, in addition to a Git repo, I need to download a binary
> file. I do it with curl in a pre or post download hook.
>
> I provided a .hash file for the package. Buildroot actually checks the Git
> tarball hash, but not the other file's. How can I force it ?

Try using PKG_EXTRA_DOWNLOADS. Buildroot should both download the files,
and check their hash. See package/asterisk/ for example.

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2025-03-26  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26  8:37 [Buildroot] how to force-check hash for extra file? David Picard
2025-03-26  9:06 ` Baruch Siach via buildroot [this message]

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=87cye4ma9z.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=david.picard@clermont.in2p3.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