From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Target to create missing hashes.
Date: Mon, 6 Apr 2015 10:56:02 +0200 [thread overview]
Message-ID: <20150406085602.GA4369@free.fr> (raw)
In-Reply-To: <5521BE08.9020304@proximus.be>
Johan, All,
On 2015-04-06 00:58 +0200, Johan Sagaert spake thusly:
> 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
Well, we do not want the hashes to be automatically created, because we
want them to come from upstream if possible, and only if upstream does
not provide hashes do we locally compute them.
So, we can't offer an automatic way to create hashes. It has to be a
manual process.
> Maybe the missing hash warnings should also be redirected to a file
> .missing_hashes, they mostly go unnoticed otherwise while building.
Well, I have a series that makes missing hashes a hard error (when the
.hash file exists), so that will be caught fairly easily! ;-) And a
missing .hash file would become a warning for now, with the ultimate
goal of making it a hard error in the future (because we do not have
enough packages with a .hash file for now).
There is the idea floatign around of creating a check-package (or
check-patch) script that could be used to validate a new package, and
checking a .hash file exists could be part of that script.
Any taker? ;-)
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-06 8:56 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
2015-04-06 8:56 ` Yann E. MORIN [this message]
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=20150406085602.GA4369@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox