Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uboot-tools: fix license issues
Date: Wed, 23 Oct 2013 11:39:44 +0200	[thread overview]
Message-ID: <20131023113944.2e370a3b@skate> (raw)
In-Reply-To: <CAAXf6LW3ob7ev6VBpG3ajRR=aMSdgN0mM=O7a7wX2+cLd6fRBA@mail.gmail.com>

Dear Thomas De Schampheleire,

On Tue, 22 Oct 2013 16:57:31 +0200, Thomas De Schampheleire wrote:

> Maybe the legal-info target should warn for non-existing files, rather
> than error out.

I disagree. Before 376c3aad61dbeb8e2126e13658fd150b70746afb
("legal-info: fail trying to copy a non-existent license file"), what
was happening is exactly what you're suggesting.

The problem is that we didn't notice when legal information were wrong,
because nobody looks at warnings, and because autobuilders result were
saying "OK" even though the legal info wasn't ok. So at the time (back
in May this year), we discussed that, and we agreed that legal-info
should error out if it cannot find a license file referenced by
<pkg>_LICENSE_FILES, so that autobuilder results loudly say that
something failed.

And interestingly, the precise reason why we noticed the legal-info
were wrong was because the autobuilder build failed, and we fixed it. I
very much prefer that than having the <pkg>_LICENSE_FILES remain wrong
for many weeks/months without anybody noticing.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2013-10-23  9:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 14:37 [Buildroot] [PATCH] uboot-tools: fix license issues Gustavo Zacarias
2013-10-22 14:57 ` Thomas De Schampheleire
2013-10-22 15:22   ` Gustavo Zacarias
2013-10-23  9:39   ` Thomas Petazzoni [this message]
2013-10-24  6:51     ` Thomas De Schampheleire
2013-10-24  8:20       ` Luca Ceresoli
2013-10-24 12:24         ` Arnout Vandecappelle
2013-10-24 12:35           ` Gustavo Zacarias
2013-10-24 19:29             ` Arnout Vandecappelle
2013-10-22 16:39 ` Peter Korsgaard
2013-10-22 16:39   ` Gustavo Zacarias
2013-10-22 17:01   ` Thomas De Schampheleire
2013-10-22 17:49     ` Peter Korsgaard
2013-10-22 17:50     ` Gustavo Zacarias
  -- strict thread matches above, loose matches on Subject: below --
2013-10-22 16:46 Gustavo Zacarias
2013-11-02 13:43 ` Thomas Petazzoni
2013-11-02 16:24   ` Gustavo Zacarias
2013-11-02 16:43     ` Thomas Petazzoni
2013-11-02 17:32       ` Yann E. MORIN
2013-11-02 17:38         ` 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=20131023113944.2e370a3b@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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