From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] dhrystone: add a hash file
Date: Wed, 2 Dec 2015 23:03:20 +0100 [thread overview]
Message-ID: <20151202220320.GJ5773@free.fr> (raw)
In-Reply-To: <87poyofulj.fsf@dell.be.48ers.dk>
Peter, Vicente, All,
On 2015-12-02 21:45 +0100, Peter Korsgaard spake thusly:
> >>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
>
> > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> > ---
> > package/dhrystone/dhrystone.hash | 2 ++
> > 1 file changed, 2 insertions(+)
> > create mode 100644 package/dhrystone/dhrystone.hash
>
> > diff --git a/package/dhrystone/dhrystone.hash b/package/dhrystone/dhrystone.hash
> > new file mode 100644
> > index 0000000..9ea22a3
> > --- /dev/null
> > +++ b/package/dhrystone/dhrystone.hash
> > @@ -0,0 +1,2 @@
> > +# Locally calculated
> > +sha256 038a7e9169787125c3451a6c941f3aca5db2d2f3863871afcdce154ef17f4e3e dhry-c
>
> Hmm, what are we going to do if this file ever changes?
That's a good question...
Since ultimately I'd like we get hash files for the packages, and make
it an error when the hash file is missing, we'd have to handle those
cases in a consistent way.
There are two options here:
- add a real hash, and break older releases when the file is updated
upstream,
- add a 'none' hash, but loose the detection tht upstream has changed
(but the autobuilders would tell us if that change breaks the
build).
I'm afraid the only possible solution if we want to have a hash is the
second solution (but with a comment explaning why it is so).
But until we make the .hash files mandatory, we can just not add it for
non-versioned upstreams. So I'd say we drop that one.
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-12-02 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 12:29 [Buildroot] [PATCH 1/4] dhrystone: add a hash file Vicente Olivert Riera
2015-12-02 12:29 ` [Buildroot] [PATCH 2/4] libglu: " Vicente Olivert Riera
2015-12-17 16:21 ` Thomas Petazzoni
2015-12-02 12:29 ` [Buildroot] [PATCH 3/4] torsmo: " Vicente Olivert Riera
2015-12-17 16:23 ` Thomas Petazzoni
2015-12-17 21:34 ` Peter Korsgaard
2015-12-02 12:29 ` [Buildroot] [PATCH 4/4] whetstone: " Vicente Olivert Riera
2015-12-17 16:23 ` Thomas Petazzoni
2015-12-02 20:45 ` [Buildroot] [PATCH 1/4] dhrystone: " Peter Korsgaard
2015-12-02 21:58 ` Arnout Vandecappelle
2015-12-02 22:03 ` Yann E. MORIN [this message]
2015-12-03 10:35 ` Vicente Olivert Riera
2015-12-03 10:44 ` Thomas Petazzoni
2015-12-03 11:42 ` Peter Korsgaard
2015-12-03 20:52 ` Peter Seiderer
2015-12-03 21:18 ` Peter Korsgaard
2015-12-17 16:20 ` 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=20151202220320.GJ5773@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