From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/2] scancpan: support more licenses
Date: Tue, 14 Aug 2018 13:33:37 +0200 [thread overview]
Message-ID: <20180814133337.5b9338b0@windsurf> (raw)
In-Reply-To: <20180813131135.32651-2-chrismcc@gmail.com>
Hello Christopher,
So, taking Arnout/Yann feedback into account.
On Mon, 13 Aug 2018 06:11:34 -0700, Christopher McCrory wrote:
> diff --git a/utils/scancpan b/utils/scancpan
> index da8e7b91ac..2070e2a233 100755
> --- a/utils/scancpan
> +++ b/utils/scancpan
> @@ -692,8 +692,19 @@ while (my ($distname, $dist) = each %dist) {
> : $dist->{license};
> # BR requires license name as in http://spdx.org/licenses/
> $license =~ s|apache_2_0|Apache-2.0|;
> + $license =~ s|apache_1_1|Apache-1.1|;
> + $license =~ s|apache|Apache-2.0|;
In this case, scancpan should not conclude that Apache-2.0 is used,
because "apache" is not specific enough. Instead, it should emit a
warning.
> $license =~ s|artistic_2|Artistic-2.0|;
> + $license =~ s|artistic|Artistic-1.0|;
> + $license =~ s|lgpl_2_1|LGPL-2.1|;
> + $license =~ s|lgpl_3_0|LGPL-3.0|;
> + $license =~ s|lgpl|LGPL-2.1|;
Same.
> + $license =~ s|bsd|BSD|;
Same.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-14 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 13:11 [Buildroot] [RFC PATCH 0/2] scancpan patches Christopher McCrory
2018-08-13 13:11 ` [Buildroot] [RFC PATCH 1/2] scancpan: support more licenses Christopher McCrory
2018-08-13 15:42 ` François Perrad
2018-08-13 16:54 ` Thomas Petazzoni
2018-08-13 17:35 ` Christopher McCrory
2018-08-13 21:16 ` Yann E. MORIN
2018-08-13 22:52 ` Arnout Vandecappelle
2018-08-14 11:33 ` Thomas Petazzoni [this message]
2018-08-15 11:57 ` Christopher McCrory
2018-08-13 13:11 ` [Buildroot] [RFC PATCH 2/2] scancpan: wrap abstract if too long Christopher McCrory
2018-08-13 16:29 ` François Perrad
2018-08-16 3:07 ` Ricardo Martincoski
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=20180814133337.5b9338b0@windsurf \
--to=thomas.petazzoni@bootlin.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