From: Rahul Bedarkar <Rahul.Bedarkar@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] Standardizing format for specifying license(s)
Date: Fri, 15 Jan 2016 17:23:34 +0530 [thread overview]
Message-ID: <5698DDBE.3000402@imgtec.com> (raw)
Hi all,
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.
With that in mind, I'm proposing following initial format which allows
ease in parsing manifest file.
* If package is licensed under multiple licenses e.g. bluez5_utils
libraries and programs are licensed under different licenses. In such
case, comma separate licenses e.g. BLUEZ5_UTILS_LICENSE=GPLv2+, LGPLv2.1+
If there is clear distinction between which component is licensed
under what license then annotate the license with libraries or programs
or others keywords. e.g. BLUEZ5_UTILS_LICENSE=GPLv2+ (programs),
LGPLv2.1+ (libraries)
* If package is dual licensed e.g. dbus then slash separate licenses.
e.g. DBUS_LICENSE = AFLv2.1 / GPLv2+
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.
Any suggestions and thoughts are welcome.
Regards,
Rahul
next reply other threads:[~2016-01-15 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 11:53 Rahul Bedarkar [this message]
2016-01-15 13:12 ` [Buildroot] Standardizing format for specifying license(s) 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
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=5698DDBE.3000402@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox