All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Bedarkar <Rahul.Bedarkar@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] Standardizing format for specifying license(s)
Date: Fri, 15 Jan 2016 20:00:31 +0530	[thread overview]
Message-ID: <56990287.7050409@imgtec.com> (raw)
In-Reply-To: <20160115144437.2d843ae1@free-electrons.com>

Hi Thomas,

On Friday 15 January 2016 07:14 PM, Thomas Petazzoni wrote:
> Rahul,
>
> On Fri, 15 Jan 2016 17:23:34 +0530, Rahul Bedarkar wrote:
>
>> In package.mk, as of now, there is no standard format for specifying
>> licenses under which package is released. In some cases we comma
>> separate licenses while in others space separated list. It's difficult
>> to parse manifest file generated by legal-info target in such cases. One
>> of requirements of parsing manifest file would be checking for license
>> compatibility of dependent packages.
>
> Makes sense. If you want to formalize the format for the <pkg>_LICENSE
> variable, then what I would suggest is that you submit some patches
> against the Buildroot manual, which is the ultimate reference for such
> things. Then we can comment on the patch itself, and progressively
> agree on defining the appropriate format, in a way that can directly be
> merged into the documentation once a consensus has been reached.
>

OK. I will send patch against manual.

>> * If package is dual licensed e.g. dbus then slash separate licenses.
>> e.g. DBUS_LICENSE = AFLv2.1 / GPLv2+
>
> We normally use "or" in this case:
>
> CPPDB_LICENSE = Boost-v1.0 or MIT
> GNU_EFI_LICENSE = BSD-3c and/or GPLv2+ (gnuefi), BSD-3c (efilib)
> LIBICAL_LICENSE = MPLv1.0 or LGPLv2.1
>
> etc.
>
> To me, using a "or" makes it really explicit, much more than a "/".
>

Yes. Agree.

>> There was effort to comma separate licenses
>> https://git.busybox.net/buildroot/log/?qt=grep&q=comma+separate+licenses
>> but just comma separating licenses in many cases is not correct from
>> point of different licensing terms and parsing manifest file.
>
> Why ? This effort done by Gustavo was only to replace cases where
> different parts of the package are covered by different licenses, and
> the changes done by Gustavo completely match point (1) of your specific
> above.

Yes, it matches with point (1). I think one exception is dbus which has 
licenses comma separated but it's dual licensed.

Overall it looks like, what I am proposing is already in place but there 
are some non conforming packages and it's not documented.

Regards,
Rahul

  reply	other threads:[~2016-01-15 14:30 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
2016-01-16  1:02     ` Arnout Vandecappelle
2016-01-15 13:44 ` Thomas Petazzoni
2016-01-15 14:30   ` Rahul Bedarkar [this message]
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=56990287.7050409@imgtec.com \
    --to=rahul.bedarkar@imgtec.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 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.