From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/faad2: add hash
Date: Sun, 14 Dec 2014 19:16:31 +0100 [thread overview]
Message-ID: <20141214181631.GC4121@free.fr> (raw)
In-Reply-To: <XnsA403BE33C127EberndkuhlsPkbjNfxxIA@bernd-kuhls.de>
Bernd, All,
On 2014-12-14 18:41 +0100, Bernd Kuhls spake thusly:
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote in
> news:1418578396-11893-1-git-send-email-yann.morin.1998 at free.fr:
>
> > +++ b/package/faad2/faad2.hash
> > @@ -0,0 +1,2 @@
> > +# Locally computed
> > +sha256 ee26ed1e177c0cd8fa8458a481b14a0b24ca0b51468c8b4c8b676fd3ceccd330 faad2-2.7.tar.gz
> just a small note because the buildroot doc says hash values provided by
> upstream are prefered:
Indeed.
> Looking at http://sourceforge.net/projects/faac/files/faad2-src/faad2-2.7/
> you can click on the "i" button of faad2-2.7.tar.bz2 to display its md5/sha1
> values, they could be added to our hash file instead of a locally computed
> hash.
OK, but it is not straight-forward. Upstream as we document it is:
http://www.audiocoding.com/faad2.html
and they have no hash that I could find on that website.
But they point the downloads to the sourceforge page.
However, I'm a bit reluctant at using hashes published by a third-party.
I guess we cn add them, plus our locally computed sha256.
Thanks for pointing this.
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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-12-14 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 17:33 [Buildroot] [PATCH] package/faad2: add hash Yann E. MORIN
2014-12-14 17:41 ` Bernd Kuhls
2014-12-14 18:09 ` Peter Korsgaard
2014-12-14 18:21 ` Yann E. MORIN
2014-12-14 18:16 ` Yann E. MORIN [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=20141214181631.GC4121@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