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 0/3] core: check hashes of license files
Date: Sun, 18 Jun 2017 10:01:01 +0200	[thread overview]
Message-ID: <cover.1497772831.git.yann.morin.1998@free.fr> (raw)

Hello All!

This small series is a proposal to check the hashes of the license files
during legal-info, to catch the packages whose license changes but where
the text of the new license is in the same file.

This was suggested by Rahul recently:
    http://lists.busybox.net/pipermail/buildroot/2017-June/194425.html


Regards,
Yann E. MORIN.


The following changes since commit 859764ac39c18c6aaabbb6a1a47f2fa2e5793044

  linux-headers: bump 4.{1, 4, 9, 11}.x series (2017-06-17 16:17:04 +0200)


are available in the git repository at:

  git://git.buildroot.org/~ymorin/git/buildroot.git

for you to fetch changes up to 41013c99543173da1ec547219c7f67e52d323a40

  docs/manual: document hashes for license files (2017-06-18 09:59:06 +0200)


----------------------------------------------------------------
Yann E. MORIN (3):
      core/pkg-util: pass package directory and name when saving license files
      core/pkg-utils: check hashes of license files
      docs/manual: document hashes for license files

 Makefile                                  |  2 +-
 docs/manual/adding-packages-directory.txt | 16 ++++++++++++++--
 package/pkg-generic.mk                    |  2 +-
 package/pkg-utils.mk                      | 11 ++++++++---
 4 files changed, 24 insertions(+), 7 deletions(-)

-- 
.-----------------.--------------------.------------------.--------------------.
|  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-18  8:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18  8:01 Yann E. MORIN [this message]
2017-06-18  8:01 ` [Buildroot] [PATCH 1/3] core/pkg-util: pass package directory and name when saving license files 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
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=cover.1497772831.git.yann.morin.1998@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