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 1/1] package/mcelog: fix legal-info
Date: Sun, 18 Jun 2017 10:02:18 +0200	[thread overview]
Message-ID: <20170618080218.GA2566@scaer> (raw)
In-Reply-To: <87zidba6ff.fsf@dell.be.48ers.dk>

Peter, Rahul, All,

On 2017-06-14 00:06 +0200, Peter Korsgaard spake thusly:
> >>>>> "Rahul" == Rahul Bedarkar <rahulbedarkar89@gmail.com> writes:
> 
>  > On Mon, Jun 12, 2017 at 9:45 AM, Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
>  >> 
>  >> README was renamed to README.md
>  >> https://git.kernel.org/pub/scm/utils/cpu/mce/mcelog.git/commit/README.md?id=2fda0091a0628480a08cbf6ebe309fcb83aeae34
> 
>  > make <pkg>-legal-info should have caught that after version bump as a
>  > part of testing. But it looks like we don't do that usually. In past,
>  > we have seen such failures after version bump.
> 
>  > To avoid such failures, we can add hash of license file in <pkg>.hash
>  > and checking that after source is downloaded. If license file changes,
>  > it will be noticed while build test after version bump.
> 
>  > Potentially, it will also help in keeping license string of packages
>  > up-to-date if it gets changed. What do you think ?
> 
> Yes, this is something I have been thinking about as well (but not found
> time to implement yet). +1 from here!

I've sent a propsal for that:
   http://lists.busybox.net/pipermail/buildroot/2017-June/194820.html

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12  4:15 [Buildroot] [PATCH 1/1] package/mcelog: fix legal-info Bernd Kuhls
2017-06-12  8:11 ` Thomas Petazzoni
2017-06-12 17:08 ` Rahul Bedarkar
2017-06-12 19:04   ` Thomas Petazzoni
2017-06-13 16:29     ` Rahul Bedarkar
2017-06-13 22:11     ` Peter Korsgaard
2017-06-13 22:06   ` Peter Korsgaard
2017-06-18  8:02     ` 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=20170618080218.GA2566@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