From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] manual: Add notes about GitHub and hashes
Date: Sun, 26 Oct 2014 09:45:02 -0700 [thread overview]
Message-ID: <20141026164502.GA3592@free.fr> (raw)
In-Reply-To: <1414341315-31896-3-git-send-email-maxime.hadjinlian@gmail.com>
Maxime, All,
On 2014-10-26 17:35 +0100, Maxime Hadjinlian spake thusly:
> We can't take hash from GitHub, unless the tarball has been uploaded by
*hashes
> the maintainer, otherwise it will generated and may change over time,
...it is generated...
> which renders hash files, useless.
>
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> docs/manual/adding-packages-directory.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
> index c145829..28312d6 100644
> --- a/docs/manual/adding-packages-directory.txt
> +++ b/docs/manual/adding-packages-directory.txt
> @@ -372,6 +372,11 @@ the hashes of the downloaded files for the +libfoo+ package.
> The hashes stored in that file are used to validate the integrity of the
> downloaded files.
>
> +If +libfoo+ is from GitHub, we can only accept +.hash+ file if the
> +package has a release section and the maintainer has uploaded a release
> +tarball. Otherwise, the automated generated tarball may change through
s/through/over/
> +time, rendering a +.hash+ file invalid.
time, and thus its hashes may be different each time it is downloaded,
making the +.hash+ file irrelevant for that tarball.
However, the .hash file is not completely irrelevant, in case the
package has extra downloads (with FOO_EXTRA_DOWNLOADS). I'm not sure if
the above makes completely sense...
Regards,
Yann E. MORIN.
> The format of this file is one line for each file for which to check the
> hash, each line being space-separated, with these three fields:
>
> --
> 2.1.1
>
--
.-----------------.--------------------.------------------.--------------------.
| 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:[~2014-10-26 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 16:35 [Buildroot] [PATCH 1/3] opencv: Remove hash file Maxime Hadjinlian
2014-10-26 16:35 ` [Buildroot] [PATCH 2/3] libevent: " Maxime Hadjinlian
2014-10-26 16:35 ` [Buildroot] [PATCH 3/3] manual: Add notes about GitHub and hashes Maxime Hadjinlian
2014-10-26 16:45 ` Yann E. MORIN [this message]
2014-10-26 17:08 ` Thomas Petazzoni
2014-10-26 17:13 ` Yann E. MORIN
2014-10-26 17:16 ` 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=20141026164502.GA3592@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