From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] legal-info too permissive?
Date: Tue, 14 May 2013 11:41:31 +0200 [thread overview]
Message-ID: <20130514114131.0b73cee0@skate> (raw)
Hello Luca,
Looking at
http://autobuild.buildroot.org/results/183/183d0af8c692b8c90b5b136999a0661fc7893b3a/build-end.log,
one can see:
cat: /home/test/test/2/output/build/neon-0.29.6/src/COPYING: No such file or directory
so it seems like the neon legal informations are not correct (or no
longer correct). This should be fixed of course, but the thing that
surprises me here is that the 'make legal-info' apparently didn't
return with an error. So the overall build was considered successful,
even though some license information is obviously wrong in this neon
package.
In this intentional? Shouldn't 'make legal-info' be more restrictive,
and bail out with an error if some license file cannot be found in the
source code? At least the latter would be the most useful behavior for
the autobuilders.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2013-05-14 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 9:41 Thomas Petazzoni [this message]
2013-05-14 9:55 ` [Buildroot] legal-info too permissive? Peter Korsgaard
2013-05-14 11:03 ` Luca Ceresoli
2013-05-14 12:50 ` Luca Ceresoli
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=20130514114131.0b73cee0@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