Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Target to create missing hashes.
Date: Mon, 6 Apr 2015 10:53:28 +0200	[thread overview]
Message-ID: <20150406105328.5976c0a9@free-electrons.com> (raw)
In-Reply-To: <5521BE08.9020304@proximus.be>

Dear Johan Sagaert,

On Mon, 06 Apr 2015 00:58:16 +0200, Johan Sagaert wrote:

> Would be nice to have a convenience make target to create missing hashes.
> (Comes in handy for custom packages not available in upstream buildroot, 
> or when bumping versions before
> posting the patches to the mailing list.)
> 
>   make  <pkg>-sha256_hash

Not sure, because we want to encourage people to look for hashes on the
upstream web site rather than generating them locally. Generating
hashes locally should be a last resort.

> Maybe the missing hash warnings should also be redirected to a file 
> .missing_hashes, they mostly go unnoticed otherwise while building.

There is a series from Yann that makes such warnings become hard
errors. However, we had to disable it because it was breaking custom
external toolchain. Another series from Yann is fixing this, but is
pending review. But clearly, this is where we want to go.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-04-06  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05 22:58 [Buildroot] Target to create missing hashes Johan Sagaert
2015-04-06  8:53 ` Thomas Petazzoni [this message]
2015-04-06  8:56 ` Yann E. MORIN
2015-04-06  9:53   ` Johan Sagaert

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=20150406105328.5976c0a9@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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