From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Standardizing format for specifying license(s)
Date: Fri, 15 Jan 2016 18:53:45 +0100 [thread overview]
Message-ID: <56993229.5060606@lucaceresoli.net> (raw)
In-Reply-To: <20160115145153.39e486e3@free-electrons.com>
Hi,
Thomas Petazzoni wrote:
> Alexander,
>
> On Fri, 15 Jan 2016 14:12:47 +0100, Alexander Dahl wrote:
>
>> If not already done, I would suggest to have those license stuff
>> compatible with SPDX [1]. I noticed license names in at least some
>> packages are not the same as the identifiers on
>> https://spdx.org/licenses/ ? so if someone wants to generate SPDX stuff
>> from a buildroot project, it maybe would be better to have a format for
>> names and delimiters which make it easier towards SPDX package data.
>
> We normally try to use the SPDX license code, at least for "new"
> licenses (i.e licenses for which we don't yet have a single Buildroot
> package under that license). However, for the first licenses (like GPL,
> LGPL, etc.), we have started using an encoding that is not the one from
> SPDX. I would personally be in favor to move to SPDX license codes
> everywhere, but that would break things for people that are currently
> parsing our license information. Is this reasonable to do nonetheless?
Changing our format to comply with SPDX would be a good idea IMHO. If
there's a well-defined and suitable standard out there it makes no
sense to define another one.
Obviously I understand this might be annoying to somebody. But we never
formally specified how "composite" licenses must be written and so,
strictly speaking, any parsing activity not based on a reliable ground.
--
Luca
next prev parent reply other threads:[~2016-01-15 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 11:53 [Buildroot] Standardizing format for specifying license(s) Rahul Bedarkar
2016-01-15 13:12 ` Alexander Dahl
2016-01-15 13:51 ` Thomas Petazzoni
2016-01-15 17:53 ` Luca Ceresoli [this message]
2016-01-16 1:02 ` Arnout Vandecappelle
2016-01-15 13:44 ` Thomas Petazzoni
2016-01-15 14:30 ` Rahul Bedarkar
2016-01-15 14:31 ` 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=56993229.5060606@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.