Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] docs/manual: document hashes for license files
Date: Sun, 25 Jun 2017 19:51:20 +0200	[thread overview]
Message-ID: <20170625175120.GF3673@scaer> (raw)
In-Reply-To: <53055153-3e6a-c7ae-0e39-3fcea6476669@lucaceresoli.net>

Luca, All,

On 2017-06-23 23:57 +0200, Luca Ceresoli spake thusly:
> 
> On 18/06/2017 10:01, Yann E. MORIN wrote:
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
> > Cc: Luca Ceresoli <luca@lucaceresoli.net>
> > Cc: Rahul Bedarkar <rahulbedarkar89@gmail.com>
> > Cc: Peter Korsgaard <peter@korsgaard.com>
> > ---
> >  docs/manual/adding-packages-directory.txt | 16 ++++++++++++++--
> >  1 file changed, 14 insertions(+), 2 deletions(-)
> > 
> > diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
> > index 08f5d42f91..5007d5368d 100644
> > --- a/docs/manual/adding-packages-directory.txt
> > +++ b/docs/manual/adding-packages-directory.txt
[--SNIP--]
> > @@ -476,6 +479,11 @@ strong hash yourself (preferably +sha256+, but not +md5+), and mention
> >  this in a comment line above the hashes.
> >  
> >  .Note
> > +The hashes for license files are used to detect a license change when a
> > +package version is bumped, so a (relatively) weak hash like +sha1+ is
> > +enough for license files.
> 
> I wouldn't spend words to say people can use a weak hash in this case.
> What's the advantage if they use weak hashes? Not computational time,
> hash files are usually small. Not ease of use: typing 'sha256sum' is not
> more difficult than 'md5sum'.
> 
> So I'd just drop that note.

OK, done. Thanks! :-)

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-06-25 17:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18  8:01 [Buildroot] [PATCH 0/3] core: check hashes of license files Yann E. MORIN
2017-06-18  8:01 ` [Buildroot] [PATCH 1/3] core/pkg-util: pass package directory and name when saving " Yann E. MORIN
2017-06-18  8:01 ` [Buildroot] [PATCH 2/3] core/pkg-utils: check hashes of " Yann E. MORIN
2017-06-23 21:49   ` Luca Ceresoli
2017-06-25 18:09     ` Yann E. MORIN
2017-06-25 21:49       ` Luca Ceresoli
2017-06-18  8:01 ` [Buildroot] [PATCH 3/3] docs/manual: document hashes for " Yann E. MORIN
2017-06-23  2:28   ` Ricardo Martincoski
2017-06-25 21:58     ` Yann E. MORIN
2017-06-23 21:57   ` Luca Ceresoli
2017-06-25 17:51     ` Yann E. MORIN [this message]
2017-06-19 17:17 ` [Buildroot] [PATCH 0/3] core: check hashes of " Rahul Bedarkar
2017-06-19 17:47   ` Yann E. MORIN
2017-06-19 19:32     ` Thomas De Schampheleire
2017-06-20 15:28       ` Yann E. MORIN
2017-06-23 21:50         ` Luca Ceresoli
2017-06-25 21:27           ` Yann E. MORIN
2017-06-20 14:49     ` Rahul Bedarkar

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=20170625175120.GF3673@scaer \
    --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